Terminal apparatus, mobility management entity (MME), and communication control method

ABSTRACT

First identification information is information indicating a mobility type supported by a core network, and second identification information is information indicating a mobility type allowed by the core network. A communication control method for a terminal apparatus of the present invention includes a step of receiving an attach accept message from the core network via a base station apparatus, the attach accept message including at least the first identification information and/or the second identification information. Accordingly, there is provided a communication procedure that is suited to the determination of a mobility type of a terminal.

TECHNICAL FIELD

The present invention relates to a terminal apparatus, a MobilityManagement Entity (MME), and a communication control method.

BACKGROUND ART

The 3rd Generation Partnership Project (3GPP), which undertakesactivities for standardizing recent mobile communication systems,discusses System Architecture Enhancement (SAE), which is systemarchitecture of the Long Term Evolution (LTE). 3GPP is in the process ofcreating specifications for the Evolved Packet System (EPS) as acommunication system that realizes an all-IP architecture. Note that acore network constituting EPS is called an Evolved Packet Core (EPC).

Further, in 3GPP, Architecture for Next Generation System (NexGen)discusses recently as a next-generation communication technique designedfor a diversity of terminals. In the NexGen, technical problems ofconnecting a diversity of terminals to a cellular network are extractedand solutions for the problems are issued as specifications.

For example, optimization of a communication procedure for a terminalrequiring high-speed communication, or optimization of a communicationprocedure for a terminal for which efficiency in power consumption needsto be enhanced to enable a battery to be maintained for several years,may be given as examples of required conditions.

Further, optimization or diversification of mobility for simultaneouslysupporting terminals with a low movement frequency, such as fixedterminals, and terminals with a high movement frequency, such asterminals provided in vehicles or the like, may also be given asexamples of required conditions.

CITATION LIST Non Patent Literature

-   NPL 1: 3rd Generation Partnership Project; Technical Specification    Group Services and System Aspects; Study on Architecture for Next    Generation System (Release 14)

SUMMARY OF INVENTION Technical Problem

In the NexGen, discussions are underway for optimization of terminalmobility.

More specifically, discussions are underway to provide mobility of agranularity suitable for a terminal through diversification of agranularity of terminal mobility.

However, procedure steps for selecting a granularity of terminalmobility or a granularity of mobility suitable for a terminal, or meansfor changing a granularity of mobility has not yet been specified.

The present invention has been made in consideration of thesecircumstances, and an object of the present invention is to providecommunication control means that provides mobility suitable forterminals and communication paths.

Solution to Problem

In order to achieve the object mentioned above, a communication controlmethod for a terminal apparatus of the present invention includes thestep of, given that first identification information is informationindicating a mobility type supported by a core network, and secondidentification information is information indicating a mobility typeallowed by the core network: receiving an attach accept message from thecore network via a base station apparatus, the attach accept messageincluding at least the first identification information and/or thesecond identification information.

Moreover, a communication control method for a Mobility ManagementEntity (MME) of the present invention includes the step of, given thatfirst identification information is information indicating a mobilitytype supported by a core network, and second identification informationis information indicating a mobility type allowed by the core network:transmitting an attach accept message to a terminal apparatus via a basestation apparatus, the attach accept message including at least thefirst identification information and/or the second identificationinformation.

Moreover, a terminal apparatus of the present invention includes, giventhat first identification information is information indicating amobility type supported by a core network, and second identificationinformation is information indicating a mobility type allowed by thecore network: a transmission and/or reception unit configured to receivean attach accept message from the core network via a base stationapparatus, the attach accept message including at least the firstidentification information and/or the second identification information.

Moreover, a Mobility Management Entity (MME) of the present inventionincludes, given that first identification information is informationindicating a mobility type supported by a core network, and secondidentification information is information indicating a mobility typeallowed by the core network: a transmission and/or reception unitconfigured to transmit an attach accept message to a terminal apparatusvia a base station apparatus, the attach accept message including atleast the first identification information and/or the secondidentification information.

Advantageous Effects of Invention

According to the present invention, a terminal can establish aconnectivity according to a mobility capability. In addition, a corenetwork can establish connections for terminals having differentmobility capabilities or establish communication paths having differentmobility capabilities.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a diagram illustrating an overview of a mobile communicationsystem.

FIG. 2 is diagram illustrating an example of a configuration of an IPmobile communication network, and the like.

FIG. 3 is diagram illustrating an example of a configuration of an IPmobile communication network, and the like.

FIG. 4 is a diagram illustrating a device configuration of an eNB.

FIG. 5 is a diagram illustrating a PDN connection establishment state.

FIG. 6 is a diagram illustrating a device configuration of an MME.

FIG. 7 is a diagram illustrating a storage unit of the MME.

FIG. 8 is a diagram illustrating the storage unit of the MME.

FIG. 9 is a diagram illustrating the storage unit of the MME.

FIG. 10 is a diagram illustrating the storage unit of the MME.

FIG. 11 is a diagram illustrating the storage unit of the MME.

FIG. 12 is a diagram illustrating the storage unit of the MME.

FIG. 13 is a diagram illustrating a device configuration of a SGW.

FIG. 14 is a diagram illustrating a storage unit of the SGW.

FIG. 15 is a diagram illustrating the storage unit of the SGW.

FIG. 16 is a diagram illustrating a device configuration of a PGW.

FIG. 17 is a diagram illustrating a storage unit of the PGW.

FIG. 18 is a diagram illustrating the storage unit of the PGW.

FIG. 19 is a diagram illustrating the storage unit of the PGW.

FIG. 20 is a diagram illustrating a device configuration of a UE.

FIG. 21 is a diagram illustrating a storage unit of the UE.

FIG. 22 is a diagram illustrating an outline of a communicationprocedure.

FIG. 23 is a diagram illustrating a PDN connectivity procedure.

FIG. 24 is a diagram illustrating a first mobility type change procedureexample.

FIG. 25 is a diagram illustrating a second mobility type changeprocedure example.

DESCRIPTION OF EMBODIMENTS

Hereinafter, a preferred embodiment for carrying out the presentinvention will be described with reference to the drawings. Note that asan example, the present embodiment describes an embodiment of a mobilecommunication system to which the present invention is applied.

1. Embodiment

1.1. System Overview

FIG. 1 is a diagram illustrating an overview of a mobile communicationsystem according to the present embodiment. As illustrated in FIG. 1, amobile communication system 1 includes a mobile terminal apparatus UE_A10, an eNB_A 45, a core network_A 90, and a PDN_A 5.

Here, the UE_A 10 may be any wirelessly connectable terminal apparatus,and may be a User equipment (UE), a Mobile equipment (ME), or a MobileStation (MS).

Alternatively, the UE_A 10 may be a CIoT terminal. Note that the CIoTterminal is an IoT terminal connectable to the core network A 90, wherethe IoT terminal includes a mobile phone terminal such as a smartphoneand may be a variety of IT equipment such as a personal computer orsensor devices.

In other words, in a case that the UE_A 10 is the CIoT terminal, theUE_A 10 may request a connection optimized for the CIoT terminal, basedon a policy of the UE_A 10 or a request from the network, or may requestthe known connection. Alternatively, the UE_A 10 may be configured as aterminal apparatus which connects to the core network_A 90 only by acommunication procedure optimized for the CIoT terminal beforehand atthe time of shipping.

Here, the core network_A 90 refers to an IP mobile communication networkrun by a Mobile Operator.

For example, the core network_A 90 may be a core network for the mobileoperator that runs and manages the mobile communication system 1, or maybe a core network for a virtual mobile operator such as a Mobile VirtualNetwork Operator (MVNO). Alternatively, the core network_A 90 may be acore network for accommodating the CIoT terminal.

Additionally, the eNB_A 45 is a base station constituting a radio accessnetwork used by the UE_A 10 to connect to the core network_A 90. Inother words, the UE_A 10 connects to the core network_A 90 by using theeNB_A 45.

Additionally, the core network_A 90 is connected to the PDN_A 5. ThePDN_A 5 is a packet data service network which provides a communicationservice to the UE_A 10, and may be configured for each service. Acommunication terminal is connected to the PDN, the UE_A 10 can transmitand/or receive user data to/from the communication terminal located inthe PDN_A 5.

Note that the user data may be data transmitted and/or received betweenthe UE_A 10 and a device included in the PDN_A 5. Note that the UE_A 10transmits the user data to the PDN_A 5 via the core network_A 90. Inother words, the UE_A 10 transmits and/or receives the user data to/fromthe core network_A 90 in order to transmit and/or receive the user datato/from the PDN_A 5. More specifically, the UE_A 10 transmits and/orreceives the user data to/from a gateway device in the core network_A90, such as a PGW_A 30 and a C-SGN_A 95, in order to transmit and/orreceive the user data to/from the PDN_A 5.

Next, an example of a configuration of the core network_A 90 will bedescribed. In the present embodiment, two configuration examples of thecore network_A 90 will be described.

FIG. 2 illustrates an example of the configuration of the corenetwork_90. The core network_A 90 in FIG. 2(a) includes a HomeSubscriber Server (HSS)_A 50, an Authentication, Authorization,Accounting (AAA)_A 55, a Policy and Charging Rules Function (PCRF)_A 60,a Packet Data Network Gateway (PGW)_A 30, an enhanced Packet DataGateway (ePDG)_A 65, a Serving Gateway (SGW)_A 35, a Mobility ManagementEntity (MME)_A 40, and a Serving GPRS Support Node (SGSN)_A 42.

Furthermore, the core network_A 90 is capable of connecting to multipleradio access networks (an LTE AN_A 80, a WLAN ANb 75, a WLAN ANa 70, aUTRAN_A 20, and a GERAN_A 25).

Such a radio access network may be configured by connecting to multipledifferent access networks, or may be configured by connecting to eitherone of the access networks. Moreover, the UE_A 10 is capable ofwirelessly connecting to the radio access network.

Moreover, a WLAN Access Network b (WLAN ANb 75) that connects to thecore network via the ePDG_A 65 and a WLAN Access Network a (WLAN ANa 75)that connects to the PGW_A, the PCRF_A 60, and the AAA_A 55 can beconfigured as access networks connectable in a WLAN access system.

Note that each device has a similar configuration to those of thedevices of the related art in a mobile communication system using EPS,and thus detailed descriptions thereof will be omitted. Each device willbe described briefly hereinafter.

The PGW_A 30 is connected to the PDN_A 5, an SGW_A 35, the ePDG_A 65,the WLAN ANa 70, the PCRF_A 60, and the AAA_A 55 and is a relay deviceconfigured to transfer user data by functioning as a gateway devicebetween the PDN_A 5 and the core network_A 90.

The SGW_A 35 is connected to the PGW 30, the MME_A 40, the LTE AN 80,the SGSN_A 42, and the UTRAN_A 20, and serves as a relay deviceconfigured to transfer user data by functioning as a gateway devicebetween the core network_A 90 and the 3GPP access network (the UTRAN_A20, the GERAN_A 25, the LTE AN_A 80).

The MME_A 40 is connected to the SGW_A 35, the LTE AN 80, and the HSS_A50, and serves as an access control device configured to performlocation information management and access control for the UE_A 10 viathe LTE AN 80. Furthermore, the core network_A 90 may include multiplelocation management devices. For example, a location management devicedifferent from the MME_A 40 may be configured. As with the MME_A 40, thelocation management device different from the MME_A 40 may be connectedto the SGW_A 35, the LTE AN 80, and the HSS_A 50.

Furthermore, in a case that multiple MMEs are included in the corenetwork_A 90, the MMEs may be connected to each other. With thisconfiguration, the context of the UE_A 10 may be transmitted and/orreceived between the MMEs.

The HSS_A 50 is connected to the MME_A 40 and the AAA_A 55 and is amanaging node configured to manage subscriber information. Thesubscriber information of the HSS_A 50 is referred to during MME_A 40access control, for example. Moreover, the HSS_A 50 may be connected tothe location management device different from the MME_A 40.

The AAA_A 55 is connected to the PGW 30, the HSS_A 50, the PCRF_A 60,and the WLAN ANa 70, and is configured to perform access control for theUE_A 10 connected via the WLAN ANa 70.

The PCRF_A 60 is connected to the PGW_A 30, the WLAN ANa 75, the AAA_A55, and the PDN_A 5 and is configured to perform QoS management on datadelivery. For example, the PCRF_A 60 manages QoS of a communication pathbetween the UE_A 10 and the PDN_A 5.

The ePDG_A 65 is connected to the PGW 30 and the WLAN ANb 75 and isconfigured to deliver user data by functioning as a gateway devicebetween the core network_A 90 and the WLAN ANb 75.

The SGSN_A 42 is connected to the UTRAN_A 20, the GERAN_A 25, and theSGW_A 35 and is a control device for location management between a 3G/2Gaccess network (UTRAN/GERAN) and the LTE access network (E-UTRAN). Inaddition, the SGSN_A 42 has functions of: selecting the PGW and the SGW;managing a time zone of the UE; and selecting the MME at the time ofhandover to the E-UTRAN.

Additionally, as illustrated in FIG. 2(b), each radio access networkincludes apparatuses to which the UE_A 10 is actually connected (such asa base station apparatus and an access point apparatus), and the like.The apparatuses used in these connections can be thought of asapparatuses adapted to the radio access networks.

In the present embodiment, the LTE AN 80 includes the eNB_A 45. TheeNB_A 45 is a radio base station to which the UE_A 10 connects in an LTEaccess system, and the LTE AN_A 80 may include one or multiple radiobase stations.

The WLAN ANa 70 is configured to include a WLAN APa 72 and a TWAG_A 74.The WLAN APa 72 is a radio base station to which the UE_A 10 connects inthe WLAN access system trusted by the operator running the corenetwork_A 90, and the WLAN ANa 70 may include one or multiple radio basestations. The TWAG_A 74 serves as a gateway device between the corenetwork_A 90 and the WLAN ANa 70. The WLAN APa 72 and the TWAG_A 74 maybe configured as a single device.

Even in a case that the operator running the core network_A 90 and theoperator running the WLAN ANa 70 are different, such a configuration canbe implemented through contracts and agreements between the operators.

Furthermore, the WLAN ANb 75 is configured to include a WLAN APb 76. TheWLAN APb 76 is a radio base station to which the UE_A 10 connects in theWLAN access system in a case that no trusting relationship isestablished with the operator running the core network_A 90, and theWLAN ANb 75 may include one or multiple radio base stations.

In this manner, the WLAN ANb 75 is connected to the core network_A 90via the ePDG_A 65, which is a device included in the core network_A 90,serving as a gateway. The ePDG_A 65 has a security function for ensuringsecurity.

The UTRAN_A 20 is configured to include a Radio Network Controller(RNC)_A 24 and an eNB (UTRAN)_A 22. The eNB (UTRAN)_A 22 is a radio basestation to which the UE_A 10 connects through a UMTS Terrestrial RadioAccess (UTRA), and the UTRAN_A 20 may include one or multiple radio basestations. Furthermore, the RNC_A 24 is a control unit configured toconnect the core network_A 90 and the eNB (UTRAN)_A 22, and the UTRAN_A20 may include one or multiple RNCs. Moreover, the RNC_A 24 may beconnected to one or multiple eNBs (UTRANs)_A 22. In addition, the RNC_A24 may be connected to a radio base station (Base Station Subsystem(BSS)_A 26) included in the GERAN_A 25.

The GERAN_A 25 is configured to include a BSS_A 26. The BSS_A 26 is aradio base station to which the UE_A 10 connects through GSM (tradename)/EDGE Radio Access (GERA), and the GERAN_A 25 may be constituted ofone or multiple radio base station BSSs. Furthermore, the multiple BSSsmay be connected to each other. Moreover, the BSS_A 26 may be connectedto the RNC_A 24.

Next, a second example of a configuration of the core network_A 90 willbe described. For example, in a case that the UE_A 10 is a CIoT device,the core network_A 90 may be configured as illustrated in FIG. 3(a). Thecore network_A 90 in FIG. 3(a) includes a CIoT Serving Gateway Node(C-SGN)_A 95 and the HSS_A 50. Note that in the same manner as FIG. 2,in order for the core network_A 90 to provide connectivity to an accessnetwork other than LTE, the core network_A 90 may include the AAA_A 55and/or the PCRF_A 60 and/or the ePDG_A 65 and/or SGSN_A 42.

The C-SGN_A 95 may be a node that incorporates some or all of thefunctions of the MME_A 40, the SGW_A 35, and the PGW_A 30 in FIG. 2. TheC-SGN_A 95 may be a node for managing establishment and disconnection ofconnectivity of the CIoT terminal, mobility of the CIoT terminal, andthe like.

In other words, the C-SGN_A 95 may have a gateway device functionbetween the PDN_A and the core network_A 90, a gateway device functionbetween the core network_A 90 and a CIOT AN_A 100, and a locationmanagement function of the UE_A 10.

As illustrated in the drawings, the UE_A 10 connects to the corenetwork_A 90 through the radio access network CIOT AN_A 100.

FIG. 3(b) illustrates the configuration of the CIOT AN_A 100. Asillustrated in the drawing, the CIOT AN_A 100 may be configuredincluding the eNB_A 45. The eNB_A 45 included in the CIOT AN_A 100 maybe the same base station as the eNB_A 45 included in the LTE AN_A 80.Alternatively, the eNB_A 45 included in the CIOT AN_A 100 may be a basestation accommodating the CIoT terminal, which is different from theeNB_A 45 included in the LTE AN_A 80.

Note that a first core network and/or a second core network may beconstituted of a system that is optimized for the IoT.

Note that herein, the UE_A 10 being connected to radio access networksrefers to the UE_A 10 being connected to a base station apparatus, anaccess point, or the like included in each of the radio access networks,data, signals, and the like being transmitted and/or received also passthrough those base station apparatuses, access points, or the like.

1.2. Device Configuration

The configuration of each apparatus will be described below.

1.2.1. eNB Configuration

The configuration of the eNB_A 45 will be described below. FIG. 4illustrates the device configuration of the eNB_A 45. As illustrated inthe drawing, the eNB_A 45 includes a network connection unit_A 420, atransmission and/or reception unit_A 430, a control unit_A 400, and astorage unit_A 440. The network connection unit_A 420, the transmissionand/or reception unit_A 430, and the storage unit_A 440 are connected tothe control unit_A 400 via a bus.

The control unit_A 400 is a function unit for controlling the eNB_A 45.The control unit_A 400 implements various processes by reading outvarious programs stored in the storage unit_A 440 and performing theprograms.

The network connection unit_A 420 is a function unit through which theeNB_A 45 connects to the MME_A 40 and/or the SGW_A 35. Further, thenetwork connection unit_A 420 is a transmission and/or receptionfunction unit with which the eNB_A 45 transmits and/or receives userdata and/or control data to/from the MME_A 40 and/or the SGW_A 35.

The transmission and/or reception unit_A 430 is a function unit throughwhich the eNB_A 45 connects to the UE_A 10. Further, the transmissionand/or reception unit_A 430 is a transmission and/or reception functionunit with which the user data and/or the control data is/are transmittedand/or received to/from the UE_A 10. Furthermore, an external antenna_A410 is connected to the transmission and/or reception unit_A 430.

The storage unit_A 440 is a function unit for storing programs, data,and the like necessary for each operation of the eNB_A 45. A storageunit 640 is constituted of, for example, a semiconductor memory, a HardDisk Drive (HDD), or the like.

The storage unit_A 440 may store at least identification informationand/or control information and/or a flag and/or a parameter included ina control message transmitted and/or received in the communicationprocedure, which will be described later.

1.2.2. MME Configuration

The configuration of the MME_A 40 will be described below. FIG. 6(a)illustrates the device configuration of the MME_A 40. As illustrated inthe drawing, the MME_A 40 includes a network connection unit_B 620, acontrol unit_B 600, and a storage unit_B 640. The network connectionunit_B 620 and the storage unit_B 640 are connected to the controlunit_B 600 via a bus.

The control unit_B 600 is a function unit for controlling the MME_A 40.The control unit_B 600 implements various processes by reading out andperforming various programs stored in the storage unit_B 640.

The network connection unit_B 620 is a function unit through which theMME_A 40 connects to the eNB_A 45 and/or the HSS_A 50 and/or the SGW_A35. In addition, the network connection unit_B 620 is a transmissionand/or reception function unit with which the MME_A 40 transmits and/orreceives user data and/or control data to/from the eNB_A 45 and/or theHSS_A 50 and/or the SGW_A 35.

The storage unit_B 640 is a function unit for storing programs, data,and the like necessary for each operation of the MME_A 40. The storageunit_B 640 is constituted of, for example, a semiconductor memory, aHard Disk Drive (HDD), or the like.

The storage unit_B 640 may store at least identification informationand/or control information and/or a flag and/or a parameter included inthe control message transmitted and/or received in the communicationprocedure, which will be described later.

As illustrated in the drawing, the storage unit_B 640 stores an MMEcontext 642, a security context 648, and MME emergency configurationdata 650. Note that the MME context includes an MM context 644 and anEPS bearer context 646. Alternatively, the MME context may include anEMM context and an ESM context. The MM context 644 may be the EMMcontext, the EPS bearer context 646 may be the ESM context.

FIG. 7(b), FIG. 8(b), and FIG. 9(b) illustrate information elements ofthe MME context stored for each UE. As illustrated in the drawings, theMME context stored for each UE includes an IMSI, anIMSI-unauthenticated-indicator, an MSISDN, an MM State, a GUTI, an MEIdentity, a Tracking Area List, a TAI of last TAU, an E-UTRAN CellGlobal Identity (ECGI), an E-UTRAN Cell Identity Age, a CSG ID, a CSGmembership, an Access mode, an Authentication Vector, a UE Radio AccessCapability, MS Classmark 2, MS Classmark 3, Supported Codecs, a UENetwork Capability, an MS Network Capability, UE Specific DRXParameters, a Selected NAS Algorithm, an eKSI, a K_ASME, NAS Keys andCOUNT, a Selected CN operator ID, a Recovery, an Access Restriction, anODB for PS parameters, an APN-OI Replacement, an MME IP address for S11,an MME TEID for S11, an S-GW IP address for S11/S4, an S GW TEID forS11/S4, an SGSN IP address for S3, an SGSN TEID for S3, an eNodeBAddress in Use for S1-MME, an eNB UE S1AP ID, an MME UE S1AP ID, aSubscribed UE-AMBR, a UE-AMBR, EPS Subscribed Charging Characteristics,a Subscribed RFSP Index, an RFSP Index in Use, a Trace reference, aTrace type, a Trigger ID, an OMC identity, a URRP-MME, CSG SubscriptionData, a LIPA Allowed, a Subscribed Periodic RAU/TAU Timer, an MPS CSpriority, an MPS EPS priority, a Voice Support Match Indicator, and aHomogenous Support of IMS Voice over PS Sessions.

The MME context for each UE may include a Mobility Type.

The IMSI is permanent identification information of a user. The IMSI isidentical to the IMSI stored in the HSS_A 50.

The IMSI-unauthenticated-indicator is instruction information indicatingthat this IMSI is not authenticated.

MSISDN represents the phone number of UE. The MSISDN is indicated by thestorage unit of the HSS_A 50.

The MM State indicates a mobility management state of the MME. Thismanagement information indicates an ECM-IDLE state in which a connectionbetween the eNB and the core network is released, an ECM-CONNECTED statein which the connection between the eNB and the core network is notreleased, or an EMM-DEREGISTERED state in which the MME does not storethe location information of the UE.

The Globally Unique Temporary Identity (GUTI) is temporaryidentification information about the UE. The GUTI includes theidentification information about the MME (Globally Unique MME Identifier(GUMMEI)) and the identification information about the UE in a specificMME (M-TMSI).

The ME Identity is an ID of the UE, and may be the IMEI/IMISV, forexample.

The Tracking Area List is a list of the tracking area identificationinformation which is assigned to the UE.

The TAI of last TAU is the tracking area identification informationindicated by a recent tracking area update procedure.

The ECGI is cell identification information of the recent UE known bythe MME_A 40.

The E-UTRAN Cell Identity Age indicates the elapsed time since the MMEacquires the ECGI.

The CSG ID is identification information of a Closed Subscriber Group(CSG), in which the UE recently operates, known by the MME.

The CSG membership is member information of the CSG of the recent UEknown by the MME. The CSG membership indicates whether the UE is the CSGmember.

The Access mode is an access mode of a cell identified by the ECGI, maybe identification information indicating that the ECGI is a hybrid whichallows access to both the UEs which is the CSG and is not the CSG

The Authentication Vector indicates a temporary Authentication and KeyAgreement (AKA) of a specific UE followed by the MME. The AuthenticationVector includes a random value RAND used for authentication, anexpectation response XRES, a key K_ASME, and a language (token) AUTNauthenticated by the network.

The UE Radio Access Capability is identification information indicatinga radio access capability of the UE.

MS Classmark 2 is a classification symbol (Classmark) of a core networkof a CS domain of 3G/2G (UTRAN/GERAN). MS Classmark 2 is used in a casethat the UE supports a Single Radio Voice Call Continuity (SRVCC) forthe GERAN or the UTRAN.

MS Classmark 3 is a classification symbol (Classmark) of a radio networkof the CS domain of the GERAN. MS Classmark 3 is used in a case that theUE supports the Single Radio Voice Call Continuity (SRVCC) for theGERAN.

The Supported Codecs is a code list supported by the CS domain. Thislist is used in the case that the UE supports SRVCC for the GERAN or theUTRAN.

The UE Network Capability includes an algorithm of security supported bythe UE and a key derivative function.

The MS Network Capability is information including at least one kind ofinformation necessary for the SGSN to the UE having the GERAN and/orUTRAN function.

The UE Specific DRX Parameters are parameters used for determining aDiscontinuous Reception (DRX) cycle length of the UE. Here, DRX is afunction for changing the UE to a low-power-consumption mode in a casethat there is no communication in a certain period of time, in order toreduce power consumption of a battery of the UE as much as possible.

The Selected NAS Algorithm is a selected security algorithm of aNon-Access Stream (NAS).

The eKSI is a key set indicating the K_ASME. The eKSI may indicatewhether to use a security key acquired by a security authentication ofthe UTRAN or the E-UTRAN.

The K_ASME is a key for E-UTRAN key hierarchy generated based on aCipher Key (CK) and an Integrity Key (IK).

The NAS Keys and COUNT includes a key K_NASint, a key K_NASenc, and aNAS COUNT parameter. The key K_NASint is a key for encryption betweenthe UE and the MME, the key K_NASenc is a key for security protectionbetween the UE and the MME. Additionally, the NAS COUNT is a count whichstarts a count in a case that a new key by which security between the UEand the MME is established is configured.

The Selected CN operator ID is identification information, which is usedfor sharing the network among operators, of a selected core networkoperator.

The Recovery is identification information indicating whether the HSSperforms database recovery.

The Access Restriction is registration information for accessrestriction.

The ODB for PS parameters indicates a state of an operator determinedbarring (ODB). Here, ODB is an access rule determined by the networkoperator (operator).

The APN-OI Replacement is a domain name substituting for APN when PGWFQDN is constructed in order to perform a DNS resolution. Thissubstitute domain name is applied to all APNs.

The MME IP address for S11 is an IP address of the MME used for aninterface with the SGW.

The MME TEID for S11 is a Tunnel Endpoint Identifier (TEID) used for theinterface with the SGW.

The S-GW IP address for S11/S4 is an IP address of the SGW used for aninterface between the MME and the SGW or between the SGSN and the MME.

The S GW TEID for S11/S4 is a TEID of the SGW used for the interfacebetween the MME and the SGW or between the SGSN and the MME.

The SGSN IP address for S3 is an IP address of the SGSN used for theinterface between the MME and the SGSN.

The SGSN TEID for S3 is a TEID of the SGSN used for the interfacebetween the MME and the SGSN.

The eNodeB Address in Use for S1-MME is an IP address of the eNBrecently used for an interface between the MME and the eNB.

The eNB UE S1AP ID is identification information of the UE in the eNB.

The MME UE S1AP ID is identification information of the UE in the MME.

The Subscribed UE-AMBR indicates the maximum value of a Maximum Bit Rate(MBR) of uplink communication and downlink communication for sharing allNon-Guaranteed Bit Rate (GBR) bearers (non-guaranteed bearers) inaccordance with user registration information.

The UE-AMBR indicates the maximum value of the MBR of the uplinkcommunication and the downlink communication which are recently used forsharing all the Non-GBR bearers (non-guaranteed bearers).

The EPS Subscribed Charging Characteristics indicate a chargingperformance of the UE. For example, the EPS Subscribed ChargingCharacteristics may indicate registration information such as normal,prepaid, a flat rate, hot billing, or the like.

The Subscribed RFSP Index is an index for a specific RRM configurationin the E-UTRAN acquired from the HSS.

The RFSP Index in Use is an index for the specific RRM configuration inthe E-UTRAN which is recently used.

The Trace reference is identification information for identifying aspecific trace record or a record set.

The Trace type indicates a type of the trace. For example, the Tracetype may indicate a type traced by the HSS and/or a type traced by theMME, the SGW, or the PGW.

The Trigger ID is identification information for identifying aconstituent element for which the trace starts.

The OMC Identity is identification information for identifying the OMCwhich receives the record of the trace.

The URRP-MME is identification information indicating that the HSSrequests UE activity notification from the MME.

The CSG Subscription Data are a relevant list of a PLMN (VPLMN) CSG IDof a roaming destination and an equivalent PLMN of the roamingdestination. The CSG Subscription Data may be associated with anexpiration date indicating an expiration date of the CSG ID and anabsent expiration date indicating that there is no expiration date foreach CSG ID. The CSG ID may be used for a specific PDN connectionthrough LIPA.

The LIPA Allowed indicates whether the UE is allowed to use the LIPA inthis PLMN, and the Subscribed Periodic RAU/TAU Timer is a timer of aperiodic RAU and/or TAU.

The MPS CS priority indicates that the UE is registered in eMLPP or a1×RTT priority service in the CS domain.

The MPS EPS priority is identification information indicating that theUE is registered in MPS in the EPS domain.

The Voice Support Match Indicator indicates whether a radio capabilityof the UE is compatible with the network configuration. For example, theVoice Support Match Indicator indicates whether the SRVCC support by theUE matches the support for voice call by the network.

The Homogenous Support of IMS Voice over PS Sessions for MME isinstruction information indicating, for each UE, whether an IMS voicecall on a PS session is supported. The Homogenous Support of IMS Voiceover PS Sessions for MME includes “Supported” in which an IP MultimediaSubsystem (IMS) voice call on a Packet Switched (PS: line switching)session in all the Tracking Areas (TAs) managed by the MME is supported,and “Not Supported” indicating a case where there is no TA in which theIMS voice call on the PS session is supported. Additionally, the MMEdoes not notify the HSS of this instruction information, in a case thatthe IMS voice call on the PS session is not uniformly supported (the TAin which the support is performed and the TA in which the support is notperformed are both present in the MME), and in a case that it is notclear whether to be supported.

FIG. 10(c) illustrates information elements included in the MME contextfor each PDN connection stored for each PDN connection. As illustratedin the drawing, the MME context for each PDN connection includes an APNin Use, an APN Restriction, an APN Subscribed, a PDN Type, an IPAddress, EPS PDN Charging Characteristics, an APN-OI Replacement, SIPTOpermissions, a Local Home Network ID, LIPA permissions, a WLANoffloadability, a VPLMN Address Allowed, a PDN GW Address in Use(control information), a PDN GW TEID for S5/S8 (control information), anMS Info Change Reporting Action, a CSG Information Reporting Action, aPresence Reporting Area Action, an EPS subscribed QoS profile, aSubscribed APN-AMBR, an APN-AMBR, a PDN GW GRE Key for uplink traffic(user data), a Default bearer, and a low access priority.

The MME context for each PDN connection may include a Mobility Type.

The APN in Use indicates APN which is recently used. This APN includesidentification information about the APN network and identificationinformation about a default operator.

The APN Restriction indicates a restriction on a combination of an APNtype to APN associated with this bearer context. In other words, the APNRestriction is information for restricting the number and types of APNswhich can be established.

The APN Subscribed refers to a registration APN received from the HSS.

The PDN Type indicates the type of the IP address. The PDN Typeindicates IPv4, IPv6, or IPv4v6, for example.

The IP Address indicates an IPv4 address or an IPv6 Prefix. Note thatthe IP address may store both the IPv4 and IPv6 prefixes.

The EPS PDN Charging Characteristics indicate a charging performance.The EPS PDN Charging Characteristics may indicate, for example, normal,prepaid, a flat rate, or hot billing.

The APN-OI Replacement is a proxy domain name of APN having the samerole as that of the APN-OI Replacement, registered for each UE. Notethat the APN-OI Replacement has a higher priority than that of theAPN-OI Replacement for each UE.

The SIPTO permissions indicate permission information to a Selected IPTraffic Offload (SIPTO) of traffic using this APN. Specifically, theSIPTO permissions identify a prohibition of the use of SIPTO, permissionof the use of SIPTO in the network excluding the local network,permission of the use of SIPTO in the network including the localnetwork, or permission of the use of SIPTO only in the local network.

The Local Home Network ID indicates identification information of a homenetwork to which the base station belongs, in a case that SIPTO(SIPTO@LN) using the local network can be used.

The LIPA permissions are identification information indicating whetherthis PDN can access through LIPA. Specifically, the LIPA permissions maybe an LIPA-prohibited which does not permit LIPA, an LIPA-only whichpermits only LIPA, or an LIPA-conditional which permits LIPA dependingon a condition.

The WLAN offload ability is identification information indicatingwhether traffic connected through this APN can perform offload to thewireless LAN by utilizing a cooperative function between the wirelessLAN and 3GPP, or maintains the 3GPP connection. The WLAN offload abilitymay vary for each RAT type. Specifically, different WLAN offloadabilities may be present for LTE (E-UTRA) and 3G (UTRA).

The VPLMN Address Allowed indicates whether a connection in which the UEuses this APN is allowed to use only an HPLMN domain (IP address) PGW inPLMN (VPLMN) of the roaming destination or allowed to use additionallythe PGW in the VPLMN domain.

The PDN GW Address in Use (control information) indicates a recent IPaddress of the PGW. This address is used when a control signal istransmitted.

The PDN GW TEID for S5/S8 (control information) is a TEID used fortransmission and/or reception of the control information in an interface(S5/S8) between the SGW and the PGW.

The MS Info Change Reporting Action is an information element indicatingthat it is necessary to notify the PGW of user location informationbeing changed.

The CSG Information Reporting Action is an information elementindicating that it is necessary to notify the PGW of CSG informationbeing changed.

The Presence Reporting Area Action indicates necessity of notificationof the change as to whether the UE is present in a Presence ReportingArea. This information element separates into identification informationof the presence reporting area and an element included in the presencereporting area.

The EPS subscribed QoS profile indicates a QoS parameter to a defaultbearer at a bearer level.

The Subscribed APN-AMBR indicates the maximum value of the Maximum BitRate (MBR) of the uplink communication and the downlink communicationfor sharing all the Non-GBR bearers (non-guaranteed bearers) establishedfor this APN in accordance with the user registration information.

The APN-AMBR indicates the maximum value of the Maximum Bit Rate (MBR)of the uplink communication and the downlink communication for sharingall the Non-GBR bearers (non-guaranteed bearers) established for thisAPN, which has been determined by the PGW.

The PDN GW GRE Key for uplink traffic (user data) is a Generic RoutingEncapsulation (GRE) key for the uplink communication of the user data ofthe interface between the SGW and the PGW.

The Default Bearer is information that is acquired and/or generated whenthe PDN connection is established, and is EPS bearer identificationinformation for identifying a default bearer associated with the PDNconnection.

Note that the EPS bearer in the present embodiment may be acommunication path that is established between the UE_A 10 and theC-SGN_A 95. In addition, the EPS bearer may include a Radio Bearer (RB)established between the UE_A 10 and the eNB_A 45 and an S1 bearerestablished between the eNB_A 45 and the C-SGN_A 95. Here, the RB andthe EPS bearer may be associated with each other on a one-to-one basis.Accordingly, identification information of the RB may be associated withidentification information of the EPS bearer on a one-to-one basis, ormay be the same as the identification information of the EPS bearer.

The EPS bearer may be a logical communication path that is establishedbetween the UE_A 10 and the PGW_A 30. In this case as well, the EPSbearer may include a Radio Bearer (RB) established between the UE_A 10and the eNB_A 45. In addition, the RB and the EPS bearer may beassociated with each other on a one-to-one basis. Accordingly,identification information of the RB may be associated withidentification information of the EPS bearer on a one-to-one basis, ormay be the same as the identification information of the EPS bearer.

Therefore, the Default Bearer may be identification information foridentifying a Signalling Radio Bearer (SRB) and/or a Control SignallingRadio Bearer (CRB), or may be identification information for identifyinga Data Radio Bearer (DRB).

Here, the SRB in the present embodiment may be RB that is originallyestablished for transmission and/or reception of control informationsuch as a control message. Here, the CRB in the present embodiment maybe RB that is originally established for transmission and/or receptionof control information such as a control message. Note that in thepresent embodiment, RB that originally serves to transmit and/or receivea control message is used to transmit and/or receive user data.Therefore, in the present embodiment, the SRB or the CRB is used totransmit and/or receive a control message and user data.

Moreover, the DRB according to the present embodiment may be RB that isestablished for transmission and/or reception of user data.

The low access priority indicates that the UE requests a low accesspriority, when the PDN connection is opened.

FIG. 1(d) illustrates the MME context stored for each bearer. Asillustrated in the drawing, the MME context stored for each bearerincludes an EPS Bearer ID, a TI, an S-GW IP address for S1-u, an S-GWTEID for S1u, a PDN GW TEID for S5/S8, a PDN GW IP address for S5/S8, anEPS bearer QoS, and a TFT.

The MME context for each bearer may include a Mobility Type.

The EPS Bearer ID is the only identification information for identifyingthe EPS bearer for a UE connection via the E-UTRAN.

Note that the EPS Bearer ID may be EPS bearer identification informationfor identifying a dedicated bearer. Therefore, the EPS bearer ID may beidentification information for identifying an EPS bearer that isdifferent from the default bearer.

Note that, as has already been described, the EPS bearer may be acommunication path that is established between the UE_A 10 and theC-SGN_A 95. In addition, the EPS bearer may include a Radio Bearer (RB)established between the UE_A 10 and the eNB_A 45 and an S1 bearerestablished between the eNB_A 45 and the C-SGN_A 95. Here, the RB andthe EPS bearer may be associated with each other on a one-to-one basis.Accordingly, identification information of the RB may be associated withidentification information of the EPS bearer on a one-to-one basis, ormay be the same as the identification information of the EPS bearer.

The EPS bearer may be a logical communication path that is establishedbetween the UE_A 10 and the PGW_A 30. In this case as well, the EPSbearer may include a Radio Bearer (RB) established between the UE_A 10and the eNB_A 45. In addition, the RB and the EPS bearer may beassociated with each other on a one-to-one basis. Accordingly,identification information of the RB may be associated withidentification information of the EPS bearer on a one-to-one basis, ormay be the same as the identification information of the EPS bearer.

Therefore, an EPS bearer ID for identifying the dedicated bearer may beidentification information for identifying a Signalling Radio Bearer(SRB) and/or a Control Signalling Radio Bearer (CRB), or may beidentification information for identifying a Data Radio Bearer (DRB).

Here, as has already been described, the SRB in the present embodimentmay be RB that is originally established for transmission and/orreception of control information such as a control message. Here, theCRB in the present embodiment may be RB that is originally establishedfor transmission and/or reception of control information such as acontrol message. Note that in the present embodiment, RB that originallyserves to transmit and/or receive a control message is used to transmitand/or receive user data. Therefore, in the present embodiment, the SRBor the CRB is used to transmit and/or receive a control message and userdata.

Moreover, the DRB in the present embodiment may be RB that isestablished for transmission and/or reception of user data.

The TI is an abbreviation of a “Transaction Identifier”, and isidentification information identifying a bidirectional message flow(Transaction).

The S-GW IP address for S1-u is an IP address of the SGW used for aninterface between the eNB and the SGW.

In a case that the user data is transmitted and/or received while beingincluded in a message for control information, the S-GW IP address forS1-u may be an IP address of the SGW used for an interface between theMME and/or the SGSN and the SGW, or may be the S-GW IP address forS11/S4.

The S-GW TEID for S1u is a TEID of the SGW used for the interfacebetween the eNB and the SGW.

In a case that the MME and/or the user data is/are transmitted and/orreceived while being included in a message for control information, theS-GW TEID for S1u may be a TEID address of the SGW used for an interfacebetween the SGSN and the SGW, or may be S-GW TEID for S11/S4.

The PDN GW TEID for S5/S8 is a TEID of the PGW for user datatransmission in the interface between the SGW and the PGW.

The PDN GW IP address for S5/S8 is an IP address of the PGW for userdata transmission in the interface between the SGW and the PGW.

The EPS bearer QoS includes a QoS Class Identifier (QCI) and anAllocation and Retention Priority (ARP). QCI indicates a class to whichthe QoS belongs. QoS can be classified in accordance with presence orabsence of band control, an allowable delay time, a packet loss rate, orthe like. The QCI includes information indicating the priority. ARP isinformation representing a priority relating to maintaining the bearer.

The TFT is an abbreviation of a “Traffic Flow Template”, and indicatesall packet filters associated with the EPS bearer.

Here, the information elements included in the MME context illustratedin FIG. 7 to FIG. 11 are included in either the MM context 644 or theEPS bearer context 646. For example, the MME context for each bearerillustrated in FIG. 11(d) may be stored in the EPS bearer context, andthe other information elements may be stored in the MM context.Alternatively, the MME context for each PDN connection illustrated inFIG. 10(c) and the MME context for each bearer illustrated in FIG. 11(d)may be stored in the EPS bearer context, and the other informationelements may be stored in the MM context.

As illustrated in FIG. 6(a), the storage unit_B 640 of the MME may storethe security context 648. FIG. 12(e) illustrates information elementsincluded in the security context 648.

As illustrated in the drawing, the security context includes an EPS ASsecurity context and an EPS NAS security context. The EPS AS securitycontext is a context relating to security of an Access Stratum (AS), andthe EPS NAS security context is a context relating to security of aNon-Access Stratum (NAS).

FIG. 12(f) illustrates information elements included in the EPS ASsecurity context. As illustrated in the drawing, the EPS AS securitycontext includes a cryptographic key, a Next Hop parameter (NH), a NextHop Chaining Counter parameter (NCC), and identifiers of the selected ASlevel cryptographic algorithms.

The cryptographic key is an encryption key in an access stratum.

The NH is an information element determined from the K_ASME. The NH isan information element for enabling a forward security.

The NCC is an information element associated with the NH. The NCCrepresents the number of occurrences of handovers in a verticaldirection changing the network.

The identifiers of the selected AS level cryptographic algorithms areidentification information of a selected encryption algorithm.

FIG. 12(g) illustrates information elements included in the EPS NASsecurity context. As illustrated in the drawing, the EPS NAS securitycontext may include the K_ASME, UE Security capabilities, and the NASCOUNT.

The K_ASME is a key for E-UTRAN key hierarchy generated based on thekeys CK and IK.

The UE Security capabilities is a set of identification informationcorresponding to a cipher and an algorithm used by the UE. Thisinformation includes information for the access stratum and informationfor the non-access stratum. Furthermore, in a case that the UE supportsaccess to the UTRAN/GERAN, this information includes information for theUTRAN/GERAN.

The NAS COUN is a counter indicating the time during which the K_ASME isoperating.

The security context 648 may be included in the MME context 642. Asillustrated in FIG. 6(a), the security context 648 and the MME context642 may be separately present.

FIG. 12(h) illustrates information elements stored in the MME emergencyconfiguration data 650. The MME emergency configuration data areinformation which is used instead of registration information of the UEacquired from the HSS. As illustrated in the drawing, the MME emergencyconfiguration data 650 include an Emergency Access Point Name (em APN),an Emergency QoS profile, an Emergency APN-AMBR, an Emergency PDN GWidentity, and a Non-3GPP HO Emergency PDN GW identity.

The em APN indicates an access point name used for the PDN connectionfor emergency.

The Emergency QoS profile indicates QoS of the default bearer of em APNat a bearer level.

The Emergency APN-AMBR indicates the maximum value of the MBR of theuplink communication and the downlink communication for sharing theNon-GBR bearers (non-guaranteed bearers) established for em APN. Thisvalue is determined by the PGW.

The Emergency PDN GW identity is identification information of the PGWstatically configured to em APN. This identification information may bean FQDN or an IP address.

The Non-3GPP HO Emergency PDN GW identity is identification informationof the PGW statically configured to em APN, in a case that the PLMNsupports a handover to an access network other than 3GPP. Thisidentification information may be an FQDN or an IP address.

Furthermore, the MME_A 40 may manage a connection state with respect tothe UE while synchronizing with the UE.

1.2.3. SGW Configuration

Hereinafter, the configuration of the SGW_A 35 will be described. FIG.13(a) illustrates the device configuration of the SGW_A 35. Asillustrated in the drawing, the SGW_A 35 includes a network connectionunit_C 1320, a control unit_C 1300, and a storage unit_C 1340. Thenetwork connection unit_C 1320 and the storage unit_C 1340 are connectedto the control unit_C 1300 via a bus.

The control unit_C 1300 is a function unit for controlling the SGW_A 35.The control unit_C 1300 implements various processes by reading out andperforming various programs stored in the storage unit_C 1340.

The network connection unit_C 1320 is a function unit through which theSGW_A 35 connects to the eNB_A 45 and/or the MME_A 40 and/or the PGW_A30 and/or SGSN_A 42. In addition, the network connection unit_C 1320 isa transmission and/or reception function unit with which the SGW_A 35transmits and/or receives user data and/or control data to/from theeNB_A 45 and/or the MME_A 40 and/or the PGW_A 30 and/or SGSN_A 42.

The storage unit_C 1340 is a function unit for storing programs, data,and the like necessary for each operation of the SGW_A 35. The storageunit_C 1340 is constituted of, for example, a semiconductor memory, aHard Disk Drive (HDD), or the like.

The storage unit_C 1340 may store at least the identificationinformation and/or the control information and/or the flag and/or theparameter included in the control message transmitted and/or received inthe communication procedure, which will be described later.

As illustrated in drawing, the storage unit_C 1340 stores an EPS bearercontext 1342. Note that the EPS bearer context includes an EPS bearercontext stored for each UE, an EPS bearer context stored for each PDN,and an EPS bearer context stored for each bearer.

FIG. 14(b) illustrates information elements of the EPS bearer contextstored for each UE. As illustrated in FIG. 14(b), the EPS bearer contextstored for each UE includes an IMSI, an MSI-unauthenticated-indicator,an ME Identity, an MSISDN, a Selected CN operator id, an MME TEID forS11, an MME IP address for S11, an S-GW TEID for S11/S4, an S-GW IPaddress for S11/S4, an SGSN IP address for S4, an SGSN TEID for S4, aTrace reference, a Trace type, a Trigger ID, an OMC identity, a Lastknown Cell Id, and a Last known Cell Id age.

Additionally, the EPS bearer context for each UE may include a MobilityType.

The IMSI is permanent identification information of a user. The IMSI isidentical to the IMSI in the HSS_A 50.

The IMSI-unauthenticated-indicator is instruction information indicatingthat this IMSI is not authenticated.

The ME Identity is identification information of the UE, and may be theIMEI/IMISV, for example.

The MSISDN represents a basic phone number of the UE. The MSISDN isindicated by the storage unit of the HSS_A 50.

The Selected CN operator id is identification information, which is usedfor sharing the network among operators, of a selected core networkoperator.

The MME TEID for S11 is a TEID of the MME used for the interface betweenthe MME and the SGW.

The MME IP address for S11 is an IP address of the MME used for theinterface between the MME and the SGW.

The S-GW TEID for S11/S4 is a TEID of the SGW used for the interfacebetween the MME and the SGW, or the interface between the SGSN and theSGW.

The S-GW IP address for S11/S4 is an IP address of the SGW used for theinterface between the MME and the SGW, or the interface between the SGSNand the SGW.

The SGSN IP address for S4 is an IP address of the SGSN used for theinterface between the SGSN and the SGW.

The SGSN TEID for S4 is a TEID of the SGSN used for the interfacebetween the SGSN and the SGW.

The Trace reference is identification information for identifying aspecific trace record or a record set.

The Trace Type indicates a type of the trace. For example, the Tracetype may indicate a type traced by the HSS and/or a type traced by theMME, the SGW, or the PGW.

The Trigger ID is identification information for identifying aconstituent element for which the trace starts.

The OMC Identity is identification information for identifying the OMCwhich receives the record of the trace.

The Last known Cell ID is recent location information of the UE notifiedby the network.

The Last known Cell ID age is information indicating the period from thetime when the Last known Cell ID is stored to the present.

Furthermore, the EPS bearer context includes an EPS bearer context foreach PDN connection stored for each PDN connection. FIG. 15(c)illustrates the EPS bearer context for each PDN connection. Asillustrated in the drawing, the EPS bearer context for each PDNconnection includes an APN in Use, EPS PDN Charging Characteristics, aP-GW Address in Use (control information), a P-GW TEID for S5/S8(control information), a P-GW Address in Use (user data), a P-GW GRE Keyfor uplink (user data), an S-GW IP address for S5/S8 (controlinformation), an S-GW TEID for S5/S8 (control information), an S GWAddress in Use (user data), a S-GW GRE Key for downlink traffic (userdata), and a Default Bearer.

The EPS bearer context for each PDN connection may include a MobilityType.

The APN in Use indicates APN which is recently used. This APN includesidentification information about the APN network and identificationinformation about a default operator. Additionally, this information isinformation acquired from the MME or the SGSN.

The EPS PDN Charging Characteristics indicate a charging performance.The EPS PDN Charging Characteristics may indicate, for example, normal,prepaid, a flat rate, or hot billing.

The P-GW Address in Use (control information) is an IP address of thePGW used when the SGW recently transmits the control information.

The P-GW TEID for S5/S8 (control information) is a TEID of the PGW usedfor transmission of the control information in the interface between theSGW and the PGW.

The P-GW Address in Use (user data) is an IP address of the PGW usedwhen the SGW recently transmits the user data.

The P-GW GRE Key for uplink (user data) is the GRE key for the uplinkcommunication of the user data of the interface between the SGW and thePGW.

The S-GW IP address for S5/S8 (control information) is an IP address ofthe SGW used for the interface of the control information between theSGW and the PGW.

The S-GW TEID for S5/S8 (control information) is a TEID of the SGW usedfor the interface of the control information between the GW and the PGW.

The S GW Address in Use (user data) is an IP address of the SGW which isrecently used when the SGW transmits the user data.

The S-GW GRE Key for downlink traffic (user data) is the GRE key of theuplink communication used for the interface of the user data between theSGW and the PGW.

The Default Bearer is information that is acquired and/or generated whenthe PDN connection is established, and is identification information foridentifying a default bearer associated with the PDN connection.

Furthermore, the EPS bearer context of the SGW includes the EPS bearercontext for each bearer. FIG. 15(d) illustrates the EPS bearer contextfor each bearer. As illustrated in the drawing, the EPS bearer contextfor each bearer includes an EPS Bearer Id, a TFT, a P-GW Address in Use(user data), a P-GW TEID for S5/S8 (user data), an S-GW IP address forS5/S8 (user data), an S-GW TEID for S5/S8 (user data), an S-GW IPaddress for S1-u, S12 and S4 (user data), an S-GW TEID for S1-u, S12 andS4 (user data), an eNodeB IP address for S1-u, an eNodeB TEID for S1-u,an RNC IP address for S12, an RNC TEID for S12, an SGSN IP address forS4 (user data), an SGSN TEID for S4 (user data), an EPS Bearer QoS, anda Charging Id.

The EPS bearer context for each bearer may include a Mobility Type.

The EPS Bearer Id is the only identification information identifying theEPS bearer for the UE connection via the E-UTRAN. That is, the EPSBearer Id is identification information for identifying the bearer. Inother words, the EPS Bearer Id is identification information of the EPSbearer. The EPS Bearer Id may be identification information foridentifying the SRB and/or the CRB, or may be identification informationfor identifying the DRB.

The TFT indicates all the packet filters associated with the EPS bearer.In other words, the TFT is information for identifying part of the userdata transmitted and/or received, and the SGW_A 35 transmits and/orreceives the user data identified by the TFT using the EPS bearerassociated with the TFT. In further other words, the SGW_A 35 transmitsand/or receives the user data identified by the TFT using the EPS bearerincluding the RB associated with the TFT.

Further, the SGW_A 35 may transmit and/or receive user data that cannotbe identified with the TFT by using the default bearer.

Further, the SGW_A 35 may store in advance the TFT in association withthe default bearer.

The P-GW Address in Use (user data) is an IP address of the PGW which isrecently used for transmission of the user data in the interface betweenthe SGW and the PGW.

The P-GW TEID for S5/S8 (user data) is a TEID of the PGW for theinterface of the user data between the SGW and the PGW.

The S-GW IP address for S5/S8 (user data) is an IP address of the SGWfor the user data received from the PGW.

The S-GW TEID for S5/S8 (user data) is a TEID of the SGW for theinterface of the user data between the SGW and the PGW.

The S-GW IP address for S1-u, S12 and S4 (user data) is an IP address ofthe SGW used for the interface between the SGW and the 3GPP accessnetwork (the LTE access network or GERAN/UTRAN).

In a case that the user data is transmitted and/or received while beingincluded in a message for control information, the S-GW IP address forS1-u, S12 and S4 (user data) may be an IP address of the SGW used for aninterface between the SGW and the MME and/or the SGSN, or may be theS-GW IP address for S11/S4.

The S-GW TEID for S1-u, S12 and S4 (user data) is a TEID of the SGW usedfor the interface between the SGW and the 3GPP access network (the LTEaccess network or GERAN/UTRAN).

In the case that the user data is transmitted and/or received whilebeing included in a message for control information, the S-GW TEID forS1-u, S12 and S4 (user data) may be a TEID of the SGW used for aninterface between the SGW and the MME and/or the SGSN, or may be S-GWTEID for S11/S4.

The eNodeB IP address for S1-u is an IP address of the eNB used fortransmission between the SGW and the eNB.

In the case that the user data is transmitted and/or received whilebeing included in a message for control information, the eNodeB IPaddress for S1-u may be an IP address of the MME used for an interfacebetween the MME and the SGW, or may be the MME IP address for S11.

The eNodeB TEID for S1-u is a TEID of the eNB used for the transmissionbetween the SGW and the eNB.

In the case that the user data is transmitted and/or received whilebeing included in a message for control information, the eNodeB TEID forS1-u may be a TEID of the MME used for an interface between the MME andthe SGW, or may be the MME TEID for S11.

The RNC IP address for S12 is an IP address of the RNC used for theinterface between the SGW and the UTRAN.

The RNC TEID for S12 is a TEID of the RNC used for the interface betweenthe SGW and the UTRAN.

The SGSN IP address for S4 (user data) is an IP address of the SGSN usedfor transmission of the user data between the SGW and the SGSN.

The SGSN TEID for S4 (user data) is a TEID of the SGSN used for thetransmission of the user data between the SGW and the SGSN.

The EPS Bearer QoS represents the QoS of this bearer, and may include anARP, a GBR, an MBR, and a QCI. Here, the ARP is information representingthe priority relating to maintaining the bearer. Additionally, theGuaranteed Bit Rate (GBR) represents a band guaranteed bit rate, and theMaximum Bit Rate (MBR) represents the maximum bit rate. The QCI can beclassified in accordance with presence or absence of band control, anallowable delay time, a packet loss rate, or the like. The QCI includesinformation indicating the priority.

The Charging Id is identification information for recording charginggenerated in the SGW and the PGW.

1.2.4. PGW Configuration

Hereinafter, the configuration of the PGW_A 30 will be described. FIG.16(a) illustrates the device configuration of the PGW_A 30. Asillustrated in the drawing, the PGW_A 30 includes a network connectionunit_D 1620, a control unit_D 1600, and a storage unit_D 1640. Thenetwork connection unit_D 1620 and the storage unit_D 1640 are connectedto the control unit_D 1600 via a bus.

The control unit_D 1600 is a function unit for controlling the PGW_A 30.The control unit_D 1600 implements various processes by reading out andperforming various programs stored in the storage unit_D 1640.

The network connection unit_D 1620 is a function unit through which thePGW_A 30 is connected to the SGW_A 35 and/or the PCRF_A 60 and/or theePDG_A 65 and/or the AAA_A 55 and/or the TWAG_A 74 and/or the PDN_A 5.In addition, the network connection unit_D 1620 is a transmission and/orreception function unit through which the PGW_A 30 transmits and/orreceives user data and/or control data to/from the SGW_A 35 and/or thePCRF_A 60 and/or the ePDG_A 65 and/or the AAA_A 55 and/or the TWAG_A 74and/or the PDN_A 5.

The storage unit_D 1640 is a function unit for storing programs, data,and the like necessary for each operation of the PGW_A 30. The storageunit_D 1640 is constituted of, for example, a semiconductor memory, aHard Disk Drive (HDD), or the like.

The storage unit_D 1640 may store at least the identificationinformation and/or the control information and/or the flag and/or theparameter included in the control message transmitted and/or received inthe communication procedure, which will be described later.

As illustrated in the drawing, the storage unit_D 1640 stores an EPSbearer context 1642. Note that the EPS bearer context may be storedseparately as an EPS bearer context stored for each UE, an EPS bearercontext stored for each APN, an EPS bearer context stored for each PDNconnection, and an EPS bearer context stored for each bearer.

FIG. 17(b) illustrates information elements included in the EPS bearercontext stored for each UE. As illustrated in the drawing, the EPSbearer context stored for each UE includes an IMSI, anIMSI-unauthenticated-indicator, an ME Identity, an MSISDN, a Selected CNoperator id, an RAT type, a Trace reference, a Trace type, a Trigger id,and an OMC identity.

The EPS bearer context for each UE may include a Mobility Type.

The IMSI is identification information to be assigned to a user usingthe UE.

The IMSI-unauthenticated-indicator is instruction information indicatingthat this IMSI is not authenticated.

The ME Identity is an ID of the UE, and may be the IMEI/IMISV, forexample.

The MSISDN represents a basic phone number of the UE. The MSISDN isindicated by the storage unit of the HSS_A 50.

The Selected CN operator ID is identification information, which is usedfor sharing the network among operators, of a selected core networkoperator.

The RAT type indicates a recent Radio Access Technology (RAT) of the UE.The RAT type may be, for example, the E-UTRA (LTE), the UTRA, or thelike.

The Trace reference is identification information for identifying aspecific trace record or a record set.

The Trace type indicates a type of the trace. For example, the Tracetype may indicate a type traced by the HSS and/or a type traced by theMME, the SGW, or the PGW.

The Trigger ID is identification information for identifying aconstituent element for which the trace starts.

The OMC Identity is identification information for identifying the OMCwhich receives the record of the trace.

Next, FIG. 17(c) illustrates the EPS bearer context stored for each APN.As illustrated in the drawing, the EPS bearer context stored for eachAPN of the PGW storage unit includes an APN in use and an APN-AMBR.

The APN in Use indicates APN which is recently used. This APN includesidentification information about the APN network and identificationinformation about a default operator. This information is acquired fromthe SGW.

The APN-AMBR indicates the maximum value of the Maximum Bit Rate (MBR)of the uplink communication and the downlink communication for sharingall the Non-GBR bearers (non-guaranteed bearers) established for thisAPN.

FIG. 18(d) illustrates the EPS bearer context for each PDN connectionstored for each PDN connection. As illustrated in the drawing, the EPSbearer context for each PDN connection includes an IP Address, a PDNtype, an S-GW Address in Use (control information), an S-GW TEID forS5/S8 (control information), an S-GW Address in Use (user data), an S-GWGRE Key for downlink traffic (user data), a P-GW IP address for S5/S8(control information), a P-GW TEID for S5/S8 (control information), aP-GW Address in Use (user data), a P-GW GRE Key for uplink traffic (userdata), an MS Info Change Reporting support indication, an MS Info ChangeReporting Action, a CSG Information Reporting Action, a PresenceReporting Area Action, a BCM, a Default Bearer, and EPS PDN ChargingCharacteristics.

The EPS bearer context for each PDN connection may include a MobilityType.

The IP Address indicates an IP address assigned to the UE for this PDNconnection. The IP address may be an IPv4 and/or IPv6 prefix.

The PDN type indicates the type of the IP address. The PDN typeindicates IPv4, IPv6, or IPv4v6, for example.

The S-GW Address in Use (control information) is an IP address of theSGW which is recently used for transmission of the control information.

The S-GW TEID for S5/S8 (control information) is a TEID of the SGW usedfor transmission and/or reception of the control information between theSGW and the PGW.

The S-GW Address in Use (user data) is an IP address of the SGW which isrecently used for transmission of the user data in the interface betweenthe SGW and the PGW.

The S-GW GRE Key for downlink traffic (user data) is the GRE key whichis assigned to be used in the downlink communication of the user datafrom the PGW to the SGW at the interface between the SGW and the PGW.

The P-GW IP address for S5/S8 (control information) is an IP address ofthe PGW used for communication of the control information.

The P-GW TEID for S5/S8 (control information) is a TEID of the PGW forcommunication of the control information which uses the interfacebetween the SGW and the PGW.

The P-GW Address in Use (user data) is an IP address of the PGW which isrecently used for transmission of the user data which uses the interfacebetween the SGW and the PGW.

The P-GW GRE Key for uplink traffic (user data) is the GRE key which isassigned for the uplink communication of the user data between the SGWand the PGW, that is, transmission of the user data from the SGW to thePGW.

The MS Info Change Reporting support indication indicates that the MMEand/or the SGSN supports a notification process of user locationinformation and/or user CSG information.

The MS Info Change Reporting Action is information indicating whetherthe MME and/or the SGSN is requested to transmit a change in the userlocation information.

The CSG Information Reporting Action is information indicating whetherthe MME and/or the SGSN is requested to transmit a change in the userCSG information. This information is separately indicated (a) for a CSGcell, (b) for a hybrid cell in which a user is a CSG member, (c) for ahybrid cell in which the user is not the CSG member, or for acombination thereof.

The Presence Reporting Area Action indicates necessity of notificationof the change as to whether the UE is present in a presence reportingarea. This information element separates into identification informationof the presence reporting area and an element included in the presencereporting area.

The Bearer Control Mode (BCM) indicates a control state of a bearernegotiated with respect to the GERAN/UTRAN.

The Default Bearer is information that is acquired and/or generated whenthe PDN connection is established, and is EPS bearer identificationinformation for identifying a default bearer associated with the PDNconnection.

The EPS PDN Charging Characteristics are a charging performance. Thecharging performance may indicate, for example, normal, prepaid, a flatrate, hot billing.

Furthermore, FIG. 19(e) illustrates the EPS bearer context stored foreach EPS bearer. As illustrated in the drawing, the EPS bearer contextincludes an EPS Bearer Id, a TFT, an S-GW Address in Use (user data), anS-GW TEID for S5/S8 (user data), a P-GW IP address for S5/S8 (userdata), a P-GW TEID for S5/S8 (user data), an EPS Bearer QoS, and aCharging Id.

The EPS context for each EPS bearer may include a Mobility Type.

The EPS Bearer Id is identification information identifying the accessof the UE via the E-UTRAN. In other words, the EPS Bearer Id isidentification information of the EPS bearer. In addition, the EPSBearer Id may be identification information for identifying the SRBand/or the CRB, or may be identification information for identifying theDRB.

The TFT is an abbreviation of a “Traffic Flow Template”, and indicatesall packet filters associated with the EPS bearer. In other words, theTFT is information for identifying part of the user data transmittedand/or received, and the PGW_A 30 transmits and/or receives the userdata identified by the TFT using the EPS bearer associated with the TFT.In further other words, the PGW_A 30 transmits and/or receives the userdata identified by the TFT by using the EPS bearer including the RBassociated with the TFT.

The PGW_A 30 may transmit and/or receive user data that cannot beidentified with the TFT by using the default bearer.

The PGW_A 30 may store in advance the TFT in association with thedefault bearer.

The S-GW Address in Use (user data) is an IP address of the SGW which isrecently used for transmission of the user data.

The S-GW TEID for S5/S8 (user data) is a TEID of the SGW forcommunication of the user data, which uses the interface between the SGWand the PGW.

The P-GW IP address for S5/S8 (user data) is an IP address of the PGWfor the user data received from the PGW.

The P-GW TEID for S5/S8 (user data) is a TEID of the PGW forcommunication of the user data between the SGW and the PGW.

The EPS Bearer QoS indicates the QoS of the bearer, and may include anARP, a GBR, an MBR, and a QCI. Here, the ARP is information representingthe priority relating to maintaining the bearer. Additionally, theGuaranteed Bit Rate (GBR) represents a band guaranteed bit rate, and theMaximum Bit Rate (MBR) represents the maximum bit rate. The QCI can beclassified in accordance with presence or absence of band control, anallowable delay time, a packet loss rate, or the like. The QCI includesinformation indicating the priority.

The Charging Id is charging identification information for identifyingthe record relating to charging generated in the SGW and the PGW.

1.2.5. UE Configuration

FIG. 20(a) illustrates a device configuration of the UE_A 10. Asillustrated in the drawing, the UE_A 10 includes a transmission and/orreception unit_F 2020, a control unit_F 2000, and a storage unit_F 2040.The transmission and/or reception unit_F 2020 and the storage unit_F2040 are connected to the control unit_F 2000 via a bus.

The control unit_F 2000 is a function unit for controlling the UE_A 10.The control unit_F 2000 implements various processes by reading out andperforming various programs stored in the storage unit_F 2040.

The transmission and/or reception unit_F 2020 is a function unit throughwhich the UE_A 10 connects to an IP access network via an LTE basestation. Furthermore, an external antenna_F 2010 is connected to thetransmission and/or reception unit_F 2020.

In other words, the transmission and/or reception unit_F 2020 is afunction unit through which the UE_A 10 connects to the eNB_A 45. Inaddition, the transmission and/or reception unit_F 2020 is atransmission and/or reception function unit with which the UE_A 10transmits and/or receives the user data and/or the control data to/fromthe eNB_A 45.

The storage unit_F 2040 is a function unit for storing programs, data,and the like necessary for each operation of the UE_A 10. The storageunit_F 2040 is constituted of, for example, a semiconductor memory, aHard Disk Drive (HDD), or the like.

The storage unit_F 2040 may store at least the identificationinformation and/or the control information and/or the flag and/or theparameter included in the control message transmitted and/or received inthe communication procedure, which will be described later.

As illustrated in the drawing, the storage unit_F 2040 stores a UEcontext 2042. Hereinafter, information elements stored in the storageunit_F 2040 will be described.

FIG. 21(b) illustrates information elements included in the UE contextstored for each UE. As illustrated in the drawing, the UE context storedfor each UE includes an IMSI, an EMM State, a GUTI, an ME Identity, aTracking Area List, a last visited TAI, a Selected NAS Algorithm, aSelected AS Algorithm, an eKSI, K_ASME, NAS Keys and COUNT, a TIN, UESpecific DRX Parameters, an Allowed CSG list, and an Operator CSG list.

The UE context for each UE may include a Mobility Type.

The IMSI is permanent identification information of a subscriber.

The EMM State indicates a mobility management state of the UE. Forexample, the EMM State may be EMM-REGISTERED in which the UE isregistered with the network (registered state) or EMM-DEREGISTERD inwhich the UE is not registered with the network (deregistered state).

GUTI is an abbreviation of “Globally Unique Temporary Identity,” and istemporary identification information on the UE. The GUTI includes theidentification information about the MME (Globally Unique MME Identifier(GUMMEI)) and the identification information about the UE in a specificMME (M-TMSI).

The ME Identity is an ID of an ME, and may be the IMEI/IMISV, forexample.

The Tracking Area List is a list of the tracking area identificationinformation which is assigned to the UE.

The last visited TAI is the tracking area identification informationincluded in the Tracking Area List, and is identification information ofthe latest tracking area that the UE visits.

The Selected NAS Algorithm is a selected security algorithm of the NAS.

The Selected AS Algorithm is a selected security algorithm of the AS.

The eKSI is a key set indicating the K_ASME. The eKSI may indicatewhether a security key acquired by a security authentication of theUTRAN or the E-UTRAN is used.

The K_ASME is a key for E-UTRAN key hierarchy generated based on thekeys CK and IK.

The NAS Keys and COUNT includes the key K_NASint, the key K_NASenc, andthe NAS COUNT. The K_NASint is a key for encryption between the UE andthe MME, the K_NASenc is a key for safety protection between the UE andthe MME. Additionally, the NAS COUNT is a count which starts a count ina case that a new key by which security between the UE and the MME isestablished is configured.

The Temporary Identity used in Next update (TIN) is temporaryidentification information used in the UE in an attach procedure or alocation information update procedure (RAU/TAU).

The UE Specific DRX Parameters are a Discontinuous Reception (DRX) cyclelength of the selected UE.

The Allowed CSG list is a list of the PLMN associated with a CSG ID of amember to which the allowed UE belongs, under the control of both theuser and the operator.

The Operator CSG list is a list of the PLMN associated with the CSG IDof a member to which the allowed UE belongs, under the control of onlythe operator.

Next, FIG. 21(c) illustrates the UE context for each PDN connectionstored for each PDN connection. As illustrated in the drawing, the UEcontext for each PDN connection includes an APN in Use, an APN-AMBR, anAssigned PDN Type, an IP Address, a Default Bearer, and a WLANoffloadability.

The UE context for each PDN connection may include a Mobility Type.

The APN in Use is APN recently utilized. This APN may includeidentification information about the network and identificationinformation about a default operator.

The APN-AMBR indicates the maximum value of the MBR of the uplinkcommunication and the downlink communication for sharing the Non-GBRbearers (non-guaranteed bearers). The APN-AMBR is established for eachAPN.

The Assigned PDN Type is a type of the PDN assigned from the network.The Assigned PDN Type may be IPv4, IPv6, or IPv4v6, for example.

The IP Address is an IP address assigned to the UE, and may be an IPv4address or an IPv6 prefix.

The Default Bearer is information that is acquired from the corenetwork_A 90 when the PDN connection is established, and is EPS beareridentification information for identifying a default bearer associatedwith the PDN connection.

The WLAN offloadability is WLAN offload permission informationindicating whether to allow for offload to the WLAN using aninterworking function between the WLAN and the 3GPP, or maintain the3GPP access.

FIG. 21(d) illustrates the UE context for each bearer stored in thestorage unit of the UE. As illustrated in the drawing, the UE contextfor each bearer includes an EPS Bearer ID, a TI, an EPS bearer QoS, anda TFT.

The UE context for each bearer may include a Mobility Type.

The EPS Bearer ID is identification information of the EPS bearer. TheEPS Bearer ID may be identification information for identifying the SRBand/or the CRB, or may be identification information for identifying theDRB.

The TI is an abbreviation of a “Transaction Identifier”, and isidentification information identifying a bidirectional message flow(Transaction).

The TFT is an abbreviation of a “Traffic Flow Template”, and indicatesall packet filters associated with the EPS bearer. In other words, theTFT is information for identifying part of the user data transmittedand/or received, and the UE_A 10 transmits and/or receives the user dataidentified by the TFT by using the EPS bearer associated with the TFT.In further other words, the UE_A 10 transmits and/or receives the userdata identified by the TFT by using the RB associated with the TFT.

Further, the UE_A 10 may transmit and/or receive user data that cannotbe identified with the TFT by using the default bearer.

Further, the UE_A 10 may store in advance the TFT in association withthe default bearer.

Further, the mobility type according to the present embodiment may beinformation indicating a granularity of the mobility.

1.3. Description of Communication Procedure

Next, a communication procedure according to the present embodiment willbe described with reference to FIG. 22.

As illustrated in FIG. 22, in the communication procedure according tothe present embodiment, a PDN connectivity procedure (S2200) isperformed first. In the PDN connectivity procedure (S2200), the UE_A 10and/or the eNB_A 45 and/or the MME_A 40 and/or the SGW_A 35 and/or thePGW_A 30 may establish a PDN connection or determine a mobility type ofthe UE_A 10.

Note that the PDN connectivity procedure in the present communicationprocedure may be performed in the attach procedure for the UE_A 10 toinitially connect to the core network_A 90. In this case, the PDNconnectivity request message may be transmitted and/or received whilebeing included in the attach request message that the UE_A 10 transmitsto the MME_A 40. Additionally, the activate default EPS bearer contextrequest message may be transmitted and/or received while being includedin the attach accept message that the MME_A 40 transmits to the UE_A 10.Additionally, the activate default EPS bearer context accept message maybe transmitted and/or received while being included in the attachcomplete message that the UE_A 10 transmits to the MME_A 40.

Based on completion of the attach procedure and/or the PDN connectivityprocedure, each device (the UE_A 10 and/or the eNB_A 45 and/or the MME_A40 and/or the SGW_A 35 and/or the PGW_A 30) changes its state to a firststate (S2204). Here, as illustrated in FIG. 5, the first state may be astate in which each device has established the PDN connection. Inaddition, the first state may be a state in which the UE_A 10 isconnected to the core network_A 90. Note that the first state may not belimited to these states. Further, the Packet Data network (PDN)connection may be a communication path that is established between theUE_A 10 and the PGW_A 30 and/or the PDN_A 5, or may be a Protocol DataUnit (PDU) or Packet Data Unit (PDU) session.

Next, a mobility type change procedure (S2206) may be performed. TheUE_A 10 and/or the eNB_A 45 and/or the MME_A 40 and/or the SGW_A 35and/or the PGW_A 30 may change the mobility type of the UE_A 10 throughthe mobility type change procedure.

Here, before describing the detailed steps of each procedure, in orderto avoid redundant descriptions, terms specific to the presentembodiment and primary identification information used in each procedurewill be described beforehand.

The mobility type according to the present embodiment may be informationindicating a granularity of the mobility.

Further, the UE_A 10 and/or the MME_A 40 may manage informationindicating capability relating to the mobility of the UE_A 10. Note thatthe information indicating capability relating to the mobility of theUE_A 10 may be information indicated using a mobility type. In otherwords, the identification information and the mobility type of the UE_A10 may be managed in association with each other. Note that in thepresent embodiment, description is given on the assumption that firstidentification information is such information indicating capabilityrelating to the mobility of the UE_A 10.

The UE_A 10 and/or the MME_A 40 may manage information indicatingcapability relating to the mobility of the core network_A 90. Note thatthe information indicating capability relating to the mobility of thecore network_A 90 may be information indicated using a mobility type. Inother words, the identification information and the mobility type of thecore network_A 90 may be managed in association with each other. Notethat in the present embodiment, description is given on the assumptionthat second identification information is such information indicatingcapability relating to the mobility of the core network_A 90.

The UE_A 10 and/or the MME_A 40 may manage information indicating themobility requested by the UE_A 10. Note that the information indicatingthe mobility requested by the UE_A 10 may be information indicated usinga mobility type. In other words, the identification information and themobility type of the UE_A 10 may be managed in association with eachother. Note that in the present embodiment, description is given on theassumption that third identification information is such informationindicating the mobility requested by the UE_A 10.

The UE_A 10 and/or the MME_A 40 may manage information indicatingmobility that the core network_A 90 allows to the UE_A 10. Note that theinformation indicating the mobility that the core network_A 90 allows tothe UE_A 10 may be information indicated using a mobility type. In otherwords, the identification information of the UE_A 10 and the mobilitytype may be managed in association with each other. Here, the mobilitytype that the core network_A 90 allows may be a mobility type that theMME_A 40 allows based on an operator policy, subscriber information, orthe like. Therefore, the mobility that the core network_A 90 allows mayin other words be a mobility type that the MME_A 40 and/or the operatorpolicy and/or the subscriber information allow(s). Note that in thepresent embodiment, description is given on the assumption that fourthidentification information is such information indicating the mobilitythat the core network_A 90 allows to the UE_A 10.

The UE_A 10 and/or the MME_A 40 may manage information indicatingmobility that is requested with respect to the communication pathestablished by the UE_A 10, such as the PDN connection or the EPSbearer. Note that the information indicating the mobility that isrequested with respect to the communication path established by the UE_A10, such as the PDN connection or the EPS bearer, may be informationindicated using a mobility type. In other words, identificationinformation of the communication path established by the UE_A 10 and themobility type may be managed in association with each other. Here, theidentification information of the communication path may beidentification information for identifying a PDN connection, such asAPN, an IP address, or a PDN connection ID, identification informationof the EPS bearer, such as an EPS bearer ID, or the like. Note that inthe present embodiment, description is given on the assumption thatfifth identification information is such information indicating themobility that is requested with respect to the communication pathestablished by the UE_A 10, such as the PDN connection or the EPSbearer.

The UE_A 10 and/or the MME_A 40 may manage information indicatingmobility that is allowed with respect to the communication pathestablished by the UE_A 10, such as the PDN connection or the EPSbearer. Note that the information indicating the mobility that isallowed with respect to the communication path established by the UE_A10, such as the PDN connection or the EPS bearer, may be informationindicated using a mobility type. In other words, identificationinformation of the communication path established by the UE_A 10 and themobility type may be managed in association with each other. Here, theidentification information of the communication path may beidentification information for identifying a PDN connection, such asAPN, an IP address, or a PDN connection ID, identification informationof the EPS bearer, such as an EPS bearer ID, or the like. Note that inthe present embodiment, description is given on the assumption thatsixth identification information is such information indicating themobility that is allowed with respect to the communication pathestablished by the UE_A 10, such as the PDN connection or the EPSbearer.

The UE_A 10 and/or the MME_A 40 may manage information indicating thatinformation indicating the mobility after establishment of the PDNconnection of the UE_A 10 is allowed to be changed. Note that theinformation indicating that information indicating the mobility afterestablishment of the PDN connection of the UE_A 10 is allowed to bechanged may be information indicated using a mobility type. In otherwords, the identification information and the mobility type of the UE_A10 may be managed in association with each other. Note that in thepresent embodiment, description is given on the assumption that seventhidentification information is such information indicating thatinformation indicating the mobility after establishment of the PDNconnection of the UE_A 10 is allowed to be changed.

The UE_A 10 and/or the MME_A 40 may manage information indicating thatinformation indicating the mobility after establishment of the PDNconnection of the core network_A 90 is allowed to be changed. Note thatthe information indicating that information indicating the mobilityafter establishment of the PDN connection of the core network_A 90 isallowed to be changed may be information indicated using a mobilitytype. In other words, the identification information and the mobilitytype of the core network_A 90 may be managed in association with eachother. Note that in the present embodiment, description is given on theassumption that eighth identification information is such informationindicating that information indicating the mobility after establishmentof the PDN connection of the core network_A 90 is allowed to be changed.

The UE_A 10 and/or the MME_A 40 may manage information indicating thatinformation indicating a mobility is requested to be changed. Note thatthe information indicating that information indicating a mobility isrequested to be changed may be information indicated using a mobilitytype after the requested change. In other words, the identificationinformation of the UE_A 10 and/or the core network_A 90 and the mobilitytype after the requested change may be managed in association with eachother. The change of the information indicating a mobility may becarried out with respect to the UE_A 10 and/or the core network_A 90, ormay be carried out with respect to the communication path for the UE_A10 and/or the core network_A 90. Note that in the present embodiment,description is given on the assumption that ninth identificationinformation is such information indicating that information indicating amobility is requested to be changed.

The UE_A 10 and/or the MME_A 40 may manage information indicating thatchange of the information indicating a mobility has been approved. Notethat the information indicating that change of the informationindicating a mobility has been approved may be information indicatedusing a mobility type after the approved change. In other words, theidentification information of the UE_A 10 and/or the core network_A 90and the mobility type after the approved change may be managed inassociation with each other. The change of the information indicating amobility may be carried out with respect to the UE_A 10 and/or the corenetwork_A 90, or may be carried out with respect to the communicationpath(s) that the UE_A 10 and/or the core network_A 90 has/have. Notethat in the present embodiment, description is given on the assumptionthat tenth identification information is such information indicatingthat change of the information indicating a mobility has been approved.

Here, the first identification information may be identificationinformation configured for the UE_A 10 in advance.

The second identification information may be identification informationconfigured for the core network_A 90 and/or the MME_A 40 in accordancewith an operator policy or an operation by a network operator.

The third identification information may be identification informationconfigured for the UE_A 10 in advance, or may be identificationinformation determined based on the first identification information.Therefore, the third identification information may be the same mobilitytype as the first identification information. Alternatively, the thirdidentification information may be a different mobility type from thefirst identification information, which is configured in accordance witha UE policy.

The fourth identification information may be identification informationconfigured for the core network_A 90 and/or the MME_A 40 in accordancewith an operator policy or an operation by a network operator. Inaddition, the fourth identification information may be identificationinformation determined based on the third identification information.

The fifth identification information may be identification informationconfigured for the UE_A 10 in advance, or may be identificationinformation determined based on the first identification information.Therefore, the fifth identification information may be the same mobilitytype as the first identification information. Alternatively, the fifthidentification information may be a different mobility type from thefirst identification information, which is configured in accordance witha UE policy. In addition, the fifth identification information may beidentification information determined in accordance with an application.Note that the UE_A 10 is capable of establishing multiple communicationpaths, and the UE_A 10 may store the fifth identification informationindicating a different mobility type for each communication path.

The sixth identification information may be identification informationconfigured for the core network_A 90 and/or the MME_A 40 in accordancewith an operator policy or an operation by a network operator. Inaddition, the sixth identification information may be identificationinformation determined based on the first identification information. Inaddition, the sixth identification information may be identificationinformation determined in accordance with an application. Note that theUE_A 10 is capable of establishing multiple communication paths, and thecore network_A 90 may store the sixth identification informationindicating a different mobility type for each communication path. TheUE_A 10 may store one or more of such identification information in theUE context. Furthermore, the UE_A 10 may store the fifth identificationinformation and/or the sixth identification information in the UEcontext for each PDN connection. More specifically, such identificationinformation may be stored in association with information foridentifying an application, information for identifying a flow, such asa Traffic Flow Template (TFT), or bearer identification information,such as an EPS bearer ID.

The seventh identification information may be identification informationconfigured for the UE_A 10 in advance, or may be identificationinformation determined based on a UE policy.

The eighth identification information may be identification informationconfigured for the core network_A 90 and/or the MME_A 40 in accordancewith an operator policy or an operation by a network operator. Inaddition, the eighth identification information may be identificationinformation determined based on the seventh identification information.

The ninth identification information may be identification informationdetermined based on one or more from among the first to sixthidentification information and/or a UE policy and/or an operator policyor an operation by a network operator. Therefore, the ninthidentification information may be the same mobility type as the firstidentification information and/or the third identification informationand/or the fifth identification information, and may be a differentmobility type from the second identification information and/or thefourth identification information and/or the sixth identificationinformation. The ninth identification information may be a differentmobility type from the first identification information and/or the thirdidentification information and/or the fifth identification information,and may be the same mobility type as the second identificationinformation and/or the fourth identification information and/or thesixth identification information.

The tenth identification information may be identification informationdetermined based on the ninth identification information and/or a UEpolicy and/or an operator policy or an operation by a network operator.Therefore, the tenth identification information may be the same mobilitytype as the ninth identification information, or may be a differentmobility type from the ninth identification information. The tenthidentification information may be identification information indicatingthat change of a mobility type has been approved, identificationinformation indicating that change of the mobility type has not beenapproved, or identification information indicating the reason for whichchange of the mobility type has not been approved.

Note that the UE_A 10 may store one or more of such identificationinformation in the UE context. Furthermore, the UE_A 10 may store thefifth identification information and/or the sixth identificationinformation in the UE context for each PDN connection. Morespecifically, such identification information may be stored inassociation with information for identifying an application, informationfor identifying a flow, such as a Traffic Flow Template (TFT), or beareridentification information, such as an EPS bearer ID.

Furthermore, the MME_A 40 may store one or more of such identificationinformation in the MME context. Furthermore, the MME_A 40 may store thefifth identification information and/or the sixth identificationinformation in the MME context for each PDN connection. Morespecifically, such identification information may be stored inassociation with information for identifying an application, informationfor identifying a flow, such as a Traffic Flow Template (TFT), or beareridentification information, such as an EPS bearer ID.

Next, specific examples of a mobility type will be described. Forexample, a first type may be a type indicating that the core network_A90 supports mobility of the UE_A 10 in the 3GPP access network.

A second type may be a type indicating that mobility of the UE_A 10 in anon-3GPP access network is supported.

A third type may be a type indicating that the core network_A 90supports mobility of the UE_A 10 between the 3GPP access network and thenon-3GPP access network.

A fourth type may be information indicating that mobility of the UE_A 10is not supported.

A fifth type may be a type indicating that handover during an activemode is supported.

A sixth type may be a type indicating that handover during the activemode is not allowed.

The sixth type may be a type indicating that handover during the activemode is not allowed and handover during an idle mode is allowed.

A seventh type may be a type indicating that handover during the idlemode is allowed.

Note that information indicated by mobility types is not limited to theabove. Further, a combination of any of the first to seventh types abovemay constitute one of the mobility types.

Note that the mobility types corresponding to respective pieces ofidentification information described above may be different mobilitytypes from each other or may be the same mobility type.

Note that in a case that the UE_A 10 and/or the eNB_A 45 and/or theMME_A 40 and/or the SGW_A 35 and/or the PGW_A 30 holds the respectivepieces of identification information, the UE_A 10 and/or the eNB_A 45and/or the MME_A 40 and/or the SGW_A 35 and/or the PGW_A 30 may havecapability indicated by the respective pieces of identificationinformation.

In the present embodiment, in a case that two or more kinds ofidentification information among the first to eighth identificationinformation are transmitted while being included in the same controlmessage, respective pieces of identification information may be includedin the control message and transmitted, or one kind of identificationinformation having meanings of respective pieces of identificationinformation may be included in the control message.

Note that respective pieces of identification information may be aninformation element implemented as the flag or the parameter.

1.3.1. Examples of PDN Connectivity Procedure

Next, examples of the PDN connectivity procedure will be described. Notethat the PDN connectivity procedure is a procedure initiated by the UE_A10 to start. Note that the PDN connectivity procedure is a procedure forestablishing the communication path via which the UE_A 10 transmitsand/or receives user data to/from the PDN_A 5. In other words, the PDNconnectivity procedure is a procedure for establishing a PDN connectionthat the UE_A 10 uses for transmitting and/or receiving user datato/from the PGW_A 30.

Note that the UE_A 10 may perform the PDN connectivity procedure withinan attach procedure performed at the time of an initial connection tothe core network_A 90, such as when powering on a terminal.Alternatively, the PDN connectivity procedure may be performed at anintended timing after the attach.

In accordance with the completion of the PDN connectivity procedure, theUE_A 10 establishes the PDN connection with the PGW 30.

Note that the UE_A 10 and/or the core network_A 90 can establishmultiple PDN connections by performing the PDN connectivity proceduremultiple times.

The UE_A 10 and/or the core network_A 90 may perform the PDNconnectivity procedure while including, in respective ones of messages,identification information indicating a different mobility type from thealready-established PDN connection, thereby newly establishing a PDNconnection of different mobility type. Note that identificationinformation indicating a different mobility type from thealready-established PDN connection may be any among the first to eighthidentification information.

Alternatively, a mobility type may be determined not for eachestablishment of a PDN connection, but a mobility type may be determinedin a PDN connectivity procedure performed at the time of an attachprocedure so that all PDN connections that are established thereaftermay use the same mobility type.

In other words, in a PDN connectivity procedure that is performed afterthe attach procedure, there is no need to perform transmission and/orreception of respective pieces of identification information fordetermining a mobility type or various processing that are based on thetransmission and/or reception of respective pieces of identificationinformation. In other words, a mobility type for the UE_A 10 may bedetermined in a PDN connectivity procedure performed within the attachprocedure.

Next, details of the examples of the PDN connectivity procedure will bedescribed.

Examples of steps of the PDN connectivity procedure will be describedbelow with reference to FIG. 23.

First, the UE_A 10 transmits a PDN connectivity request message to theMME_A 40 (S2302). Note that the UE_A 10 may transmit the PDNconnectivity request message to the eNB_A 45, and the transmitted PDNconnectivity request message may be transferred to the MME_A 40 via theeNB_A 45.

The UE_A 10 may include at least the first identification informationand/or the third identification information and/or the fifthidentification information and/or the seventh identification informationin the PDN connectivity request message. By transmitting the PDNconnectivity request message while including the first identificationinformation and/or the third identification information and/or the fifthidentification information and/or the seventh identification informationin the PDN connectivity request message, the UE_A 10 may requestestablishment of a PDN connection for which a mobility type can bechanged, or may indicate the requested mobility type of the UE_A 10.

For example, the UE_A 10 may request establishment of a PDN connectionand/or default bearer of a mobility type corresponding to any type fromamong the first to seventh types and/or a type obtained by combining anyof the first to seventh types as a mobility type of the UE_A 10.

Further, the UE_A 10 may request establishment of a PDN connectionand/or a default bearer of a mobility type other than the first toseventh types instead of any type from among the first to seventh types.

Further, the UE_A 10 may transmit an APN while being included in the PDNconnectivity request message. Note that the UE_A 10 may includedifferent APNs in the PDN connectivity request message to requestestablishment of different PDN connections.

Alternatively, in the case of performing the PDN connectivity procedurein the attach procedure, the UE_A 10 may notify the core network_A 90 ofthe APN using a different method. For example, instead of including theAPN in the PDN connectivity request message, the UE_A 10 may transmitthe APN while being included in another control message that the UE_A 10transmits to the core network_A 90 in the attach procedure.

The MME_A 40 receives the PDN connectivity request message. In addition,based on the reception of the PDN connectivity request message, theMME_A 40 acquires the first identification information and/or the thirdidentification information and/or the fifth identification informationand/or the seventh identification information.

Based on information included in the PDN connectivity request messageand/or the subscriber information and/or the operator policy and/or theidentification information held by the MME_A 40, the MME_A 40 maydetermine establishment of a PDN connection with the UE_A 10 and/ordetermine a mobility type of the UE_A 10.

For example, the MME_A 40 may determine the mobility type indicated bythe third identification information and/or the fifth identificationinformation as the mobility type of the UE_A 10.

Further, instead of the mobility type indicated by the thirdidentification information and/or the fifth identification information,the MME_A 40 may determine a default mobility type and/or a mobilitytype based on the subscriber information or the operator policy as themobility type of the UE_A 10.

Further, based on the reception of the first identification informationand/or the seventh identification information, the MME_A 40 maydetermine that a PDN connection and/or a default bearer for which themobility type can be changed is to be established.

Note that the MME_A 40 may indicate any type from among the first toseventh types and/or a type obtained by combining any of the first toseventh types as the mobility type of the UE_A 10.

The MME_A 40 may indicate a type other than the first to seventh types,instead of any type from among the first to seventh types, as themobility type of the UE_A 10.

Note that the mobility type of the UE_A 10 may be a mobility typecorresponding to the PDN connection to be established, a mobility typecorresponding to the default bearer, or a mobility type corresponding tothe EPS bearer.

The MME_A 40 may transmit the determined mobility type of the UE_A 10while being included in the fourth identification information and/or thesixth identification information.

Furthermore, the MME_A 40 may transmit the fourth identificationinformation and/or the sixth identification information whileassociating with a TFT.

Note that determination of the mobility type of the UE_A 10 is notlimited to the above.

Based on the reception of the PDN connectivity request message and/orthe determination of the mobility type, the MME_A 40 transmits a createsession request message to the SGW_A 35 (S2304).

The MME_40 may transmit at least the first identification informationand/or the third identification information and/or the fifthidentification information and/or the seventh identification informationand/or the fourth identification information and/or the sixthidentification information while being included in the create sessionrequest message.

Here, in the description above, the MME_A 40 is described as determiningthe mobility type, but in place of the MME_A 40, the PGW_A 30 maydetermine the mobility type of the UE_A 10. In this case, the MME_A 40may transmit the create session request message without including thefourth identification information and/or the sixth identificationinformation.

The SGW_A 35 receives the create session request message. In addition,based on the reception of the create session request message, the SGW_A35 acquires the first identification information and/or the thirdidentification information and/or the fifth identification informationand/or the seventh identification information and/or the fourthidentification information and/or the sixth identification information.

Based on the reception of the create session request message, the SGW_A35 transmits the create session request message to the PGW_A 30 (S2306).

The SGW_A 35 may transmit at least the first identification informationand/or the third identification information and/or the fifthidentification information and/or the seventh identification informationand/or the fourth identification information and/or the sixthidentification information while being included in the create sessionrequest message.

Next, the PGW_A 30 receives the create session request message. Inaddition, based on the reception of the create session request message,the PGW_A 30 acquires the first identification information and/or thethird identification information and/or the fifth identificationinformation and/or the seventh identification information and/or thefourth identification information and/or the sixth identificationinformation.

Based on information included in the create session request messageand/or the subscriber information and/or the operator policy and/or theidentification information held by the PGW_A 30, the PGW_A 30 maydetermine the mobility type for the UE_A 10.

For example, the PGW_A 30 may determine the mobility type indicated bythe third identification information and/or the fifth identificationinformation as the mobility type of the UE_A 10.

Instead of the mobility type indicated by the third identificationinformation and/or the fifth identification information, the PGW_A 30may determine a default mobility type and/or a mobility type based onthe subscriber information or the operator policy as the mobility typeof the UE_A 10.

Based on the reception of the first identification information and/orthe seventh identification information, the PGW_A 30 may determine thata PDN connection and/or a default bearer for which the mobility type canbe changed is to be established.

Note that the PGW_A 30 may indicate any type from among the first toseventh types and/or a type obtained by combining any of the first toseventh types as the mobility type of the UE_A 10.

The PGW_A 30 may indicate a type other than the first to seventh typesinstead of any type from among the first to seventh types as themobility type of the UE_A 10.

Note that the mobility type of the UE_A 10 may be a mobility typecorresponding to the PDN connection to be established, a mobility typecorresponding to the default bearer, or a mobility type corresponding tothe EPS bearer.

The PGW_A 30 may transmit the determined mobility type of the UE_A 10while being included in the fourth identification information and/or thesixth identification information.

Furthermore, the PGW_A 30 may transmit the fourth identificationinformation and/or the sixth identification information whileassociating a TFT.

Note that determination of the mobility type of the UE_A 10 is notlimited to the above.

Here, in the description above, a case is described that the PGW_A 30determines the mobility type of the UE_A 10, but in a case that theMME_A 40 has determined the mobility type of the UE_A 10, the PGW_A 30may not determine a mobility type of the UE_A 10.

In other words, in the case that the PGW_A 30 has received the fourthidentification information and/or the sixth identification information,the PGW_A 30 may not determine the mobility type of the UE_A 10.

Based on the reception of the create session request message and/or thedetermination of the mobility type, the PGW_A 30 transmits a createsession response message to the SGW_A 35 (S2310).

The PGW_A 30 may include at least the second identification informationand/or the fourth identification and/or the sixth identificationinformation and/or the eighth identification information in the createsession response message.

Note that the create session response message may be a response messagecorresponding to the create session request message.

The SGW_A 35 receives the create session response message. In addition,based on the reception of the create session response message, the SGW_A35 acquires the second identification information and/or the fourthidentification information and/or the sixth identification informationand/or the eighth identification information.

Based on the reception of the create session response message, the SGW_A35 transmits the create session response message to the MME_A 40(S2312).

The SGW_A 35 may include at least the second identification informationand/or the fourth identification information and/or the sixthidentification information and/or the eighth identification informationin the create session response message.

The MME_A 40 receives the create session response message. In addition,based on the reception of the create session response message, the MME_A40 acquires the second identification information and/or the fourthidentification information and/or the sixth identification informationand/or the eighth identification information.

Based on the reception of the create session response message, the MME_A40 transmits an activate default EPS bearer context request message tothe eNB_A 45 (S2314).

The MME_A 40 may include at least the second identification informationand/or the fourth identification information and/or the sixthidentification information and/or the eighth identification informationin the activate default EPS bearer context request message.

Note that the activate default EPS bearer context request message may bea response message to the PDN connectivity request message.

The MME_A 40 may transmit an APN and/or a PDN address and/or an EPSbearer ID while being included in the activate default EPS bearercontext request message.

Note that the MME_A 40 may include an APN and/or a PDN address and/or anEPS bearer ID in the activate default EPS bearer context request messageto identify a PDN connection and/or a default bearer to be established.For example, the MME_A 40 may include different APNs and/or differentPDN addresses and/or different EPS bearer IDs in the activate defaultEPS bearer context request message to indicate that different PDNconnections are to be established.

In addition, the MME_A 40 may store the transmitted APN and/or PDNaddress and/or EPS bearer ID in the MME context.

The MME_A 40 may store the information indicated by respective pieces oftransmitted identification information in association with thetransmitted APN and/or PDN address and/or EPS bearer ID.

The eNB_A 45 receives the activate default EPS bearer context requestmessage and transmits to the UE_A 10 an RRC message including theactivate default EPS bearer context request message (S2316). Note thatthe RRC message may be an RRC connection reconfiguration requestmessage.

The UE_A 10 receives the RRC message including the activate default EPSbearer context request message. Furthermore, in a case that the secondidentification information and/or the fourth identification informationand/or the sixth identification information and/or the eighthidentification information is included in the activate default EPSbearer context request message, the UE_A 10 acquires respective piecesof identification information.

Based on the reception of the activate default EPS bearer contextrequest message, the UE_A 10 may receive the APN and/or the PDN addressand/or the EPS bearer ID.

Note that based on the received APN and/or PDN address and/or EPS bearerID, the UE_A 10 may identify a PDN connection and/or a default bearer tobe established. For example, based on reception of different APNs and/ordifferent PDN addresses and/or different EPS bearer IDs, the UE_A 10 mayidentify establishment of different PDN connections and/or differentdefault bearers.

The UE_A 10 may store the received APN and/or PDN address and/or EPSbearer ID in the UE context.

The UE_A 10 may store the information indicated by respective pieces ofreceived identification information in association with the received APNand/or PDN address and/or EPS bearer ID.

Based on the reception of the activate default EPS bearer contextrequest message and/or the information included in the activate defaultEPS bearer context request message, the UE_A 10 may identifyestablishment of a PDN connection and/or a default bearer for which themobility type can be changed and/or identify the determined mobilitytype of the UE_A 10.

More specifically, based on the reception of the second identificationinformation and/or the eighth identification information, the UE_A 10may identify that a PDN connection and/or a default bearer for which themobility type can be changed has been established.

The UE_A 10 may identify the mobility type indicated by the receivedfourth identification information and/or sixth identificationinformation as the mobility type of the UE_A 10.

In order to respond to the received RRC message, the UE_A 10 transmitsan RRC message to the eNB_A 45 (S2318). The RRC message may be an RRCconnection reconfiguration complete message.

The eNB_A 45 receives an RRC connection reconfiguration message, andtransmits a bearer configuration message to the MME_A 40, based on thereception (S2320).

Further, based on the reception of the activate default EPS bearercontext request message, the UE_A 10 transmits the RRC message includingan activate default EPS bearer context accept message to the eNB_A 45(S2322). Here, the activate default EPS bearer context accept messagemay be a response message to the activate default EPS bearer contextrequest message.

Note that the RRC message transmitted while including the activatedefault EPS bearer context accept message may be a Direct Transfermessage.

The eNB_45 receives the RRC message including the activate default EPSbearer context accept message and transmits the activate default EPSbearer context accept message to the MME_A 40 (S2324).

The MME_A 40 receives the activate default EPS bearer context acceptmessage.

Based on the reception of the activate default EPS bearer context acceptmessage, the MME_A 40 may transmit a modify bearer request message tothe SGW_A 35 (S2326).

The SGW_A 35 receives the modify bearer request message.

Based on the reception of the modify bearer request message, the SGW_A35 transmits a modify bearer response message to the MME_A 40 (S2328).

Note that the modify bearer response message may be a response messageto the modify bearer request message.

The MME_A 40 receives the modify bearer response message.

By the above-described steps, the UE_A 10 connects to the network, andcompletes the PDN connectivity procedure. According to the completion ofthe PDN connectivity procedure, the UE_A 10 and/or the core network_A 90establishes a PDN connection and/or a default bearer. Further, accordingto the completion of the PDN connectivity procedure, the UE_A 10 and/orthe core network_A 90 may establish an EPS bearer.

In other words, based on the transmission and/or reception of theactivate default EPS bearer context request message and/or the activatedefault EPS bearer context accept message, the UE_A 10 and/or the corenetwork_A 90 establishes the PDN connection and/or the default bearer.

Further, according to the completion of the PDN connectivity procedure,the UE_A 10 and/or the core network_A 90 may determine the mobility typeof the UE_A 10 corresponding to the established PDN connection and/ordefault bearer and/or the mobility type of the UE_A 10 corresponding tothe established EPS bearer.

Note that, by the PDN connectivity procedure, the UE_A 10 can acquirethe UE context illustrated in any of FIGS. 21(b) to 21(d) from the corenetwork_A 90, and store the UE context.

More specifically, by the PDN connectivity procedure, the UE_A 10 canacquire the selected mobility type of the UE_A 10 from the corenetwork_A 90, and store the mobility type in a UE context for each PDNconnection and/or a UE context for each bearer.

In other words, based on the reception of the activate default EPSbearer context request message and/or the transmission of the activatedefault EPS bearer context accept message, the UE_A 10 can store themobility type of the UE_A 10 selected in association with a PDNconnection and/or a default bearer and/or an EPS bearer to beestablished and/or information relating to the mobility type.

More specifically, based on the reception of the activate default EPSbearer context request message and/or the reception of the activatedefault EPS bearer context accept message, the UE_A 10 can store theselected mobility type of the UE_A 10 and/or information relating themobility type in a UE context for each PDN connection and/or a UEcontext for each bearer.

Note that the information relating to the mobility type may be thesecond identification information and/or the fourth identificationinformation and/or the sixth identification information and/or theeighth identification information.

By the PDN connectivity procedure, the MME_A 40 can store the selectedmobility type of the UE_A 10 in an MME context for each PDN connectionand/or an MME context for each EPS bearer.

In other words, based on the reception of the activate default EPSbearer context request message and/or the reception of the activatedefault EPS bearer context accept message, the MME_A 40 can store themobility type of the UE_A 10 selected in association with a PDNconnection and/or a default bearer to be established and/or informationrelating to the mobility type.

More specifically, based on the reception of the activate default EPSbearer context request message and/or the reception of the activatedefault EPS bearer context accept message, the MME_A 40 can store theselected mobility type of the UE_A 10 and/or information relating themobility type in an MME context for each PDN connection and/or an MMEcontext for each EPS bearer.

By the PDN connectivity procedure, the SGW_A 35 and/or the PGW_A 30 canstore the selected mobility type of the UE_A 10 in an EPS bearer contextfor each PDN connection and/or an EPS bearer context for each EPSbearer.

Note that the UE_A 10 may perform the PDN connectivity proceduredescribed above multiple times to establish multiple PDN connections. Atthis time, respective pieces of identification information determined inthe PDN connectivity procedures to be transmitted and/or received maydiffer in the PDN connectivity procedures.

For example, an APN, an IP address, and a bearer ID may be informationthat differ in the PDN connections. Further, part or all of the first totenth identification information may be information that differ in thePDN connections.

By the PDN connection described above, the mobility type for the UE_A 10or a mobility type for a PDN connection established by the UE_A 10 canbe determined.

1.3.1.1. Modified Examples of PDN Connectivity Procedure

Regarding the core network_A 90 in the PDN connectivity procedureexample described above, a PDN connectivity procedure is described for acase adopting a core network configured to include the MME_A 40, theSGW_A 35, and the PGW_A 30 described with reference to FIG. 2; however,the core network_A 90 may be configured to include different controldevices that are other than the MME_A 40, the SGW_A 35, and the PGW_A30.

In this case, an NAS message, such as the PDN connectivity requestmessage or the activate default EPS bearer context accept messagedescribed in the present procedure and transmitted by the UE_A 10, isreceived not by the MME_A 40 but a control device in the core network_A90.

Accordingly, the reception and the processes of the NAS message by theMME_A 40 in the above description can be replaced with those performedby the control device in the core network_A 90.

Furthermore, the transmission and the processes of the NAS message suchas the activate default EPS bearer context request message or the likeby the MME_A 40 in the above description can be replaced with thoseperformed by the control device in the core network_A 90.

1.3.2. Mobility Type Change Procedure Example

First, an example of a mobility type change procedure will be described.Note that the mobility type change procedure is a procedure initiated bythe UE_A 10 and/or the core network_A 90 to start. In other words, themobility type change procedure may be a procedure initiated by the UE_A10 to start and a procedure initiated by the MME_A 40 and/or the PGW_A30 to start.

Note that the mobility type change procedure is a procedure for the UE_A10 and/or the MME_A 40 and/or the PGW_A 30 to change a mobility type ofthe UE_A 10.

Note that start of the mobility type change procedure by the UE_A 10and/or the MME_A 40 and/or the PGW_A 30 may correspond to the timing atwhich the attach procedure and/or the PDN connectivity procedure iscompleted. Regardless of the above, the UE_A 10 and/or the MME_A 40and/or the PGW_A 30 may start the mobility type change procedure at anarbitrary timing provided that the UE_A 10 is connected to the corenetwork_A 90.

Note that a trigger to start the mobility type change procedure may bean operation of the UE_A 10, the operator policy, or the subscriberinformation.

More specifically, a trigger to start the mobility type change procedureinitiated by the UE_A 10 may be based on an operation of the UE_A 10.

A trigger to start the mobility type change procedure initiated by thecore network_A 90 may be based on the network policy of the operator orthe subscriber information, rather than on reception of a bearerresource modification request message transmitted by the UE_A 10.

Due to the completion of the mobility type change procedure, the UE_A 10and/or the MME_A 40 and/or the PGW_A 30 become able to perform handoverbased on a new mobility type.

Note that below, details will be described of the mobility type changeprocedure initiated by the UE_A 10 as a first mobility type changeprocedure example. Further, details will be described of the mobilitytype change procedure initiated by the core network_A 90 as a secondmobility type change procedure example.

1.3.2.1. First Mobility Type Change Procedure Example

The first mobility type change procedure is a mobility type changeprocedure initiated by the UE_A 10.

Examples of steps of the first mobility type change procedure will bedescribed below with reference to FIG. 24.

First, the UE_A 10 transmits a bearer resource modification requestmessage to the MME_A 40 (S2402). Note that the UE_A 10 may transmit thebearer resource modification request message to the eNB_A 45, and thetransmitted bearer resource modification request message may betransferred to the MME_A 40 via the eNB 45.

The UE_A 10 may include at least the ninth identification information inthe bearer resource modification request message. By transmitting thebearer resource modification request message while including the ninthidentification information, the UE_A 10 may request change of themobility type of the UE_A 10 or request a mobility type of the UE_A 10after the requested change.

Note that the ninth identification information may be informationindicating a different mobility type from the mobility type indicated bythe second identification information and/or the fourth identificationinformation and/or the sixth identification information that the UE_A 10has acquired from the core network_A 90.

For example, the UE_A 10 may request change of the mobility type of theUE_A 10 to any type from among the first to seventh types and/or a typeobtained by combining any of the first to seventh types, or may requestchange of the mobility type to a type other than the first to seventhtypes instead of any type from among the first to seventh types.

The MME_A 40 receives the bearer resource modification request message.Further, based on the reception of the bearer resource modificationrequest message, the MME_A 40 acquires the ninth identificationinformation.

Based on information included in the bearer resource modificationrequest message and/or the subscriber information and/or the operatorpolicy and/or the identification information held by the MME_A 40, theMME_A 40 may determine change of the mobility type with respect to theUE_A 10 and/or a mobility type of the UE_A 10 after the change.

For example, the MME_A 40 may determine the mobility type indicated bythe ninth identification information as the mobility type of the UE_A 10after the change.

Instead of the mobility type indicated by the ninth identificationinformation, the MME_A 40 may determine a default mobility type and/or amobility type based on the subscriber information or the operator policyas the mobility type of the UE_A 10 after the change.

Note that the MME_A 40 may indicate any type from among the first toseventh types and/or a type obtained by combining any of the first toseventh types as the mobility type of the UE_A 10.

The MME_A 40 may indicate a type other than the first to seventh types,instead of any type from among the first to seventh types, as themobility type of the UE_A 10.

Note that the mobility type of the UE_A 10 may be a mobility typecorresponding to the PDN connection, a mobility type corresponding tothe default bearer, or a mobility type corresponding to the EPS bearer.

The MME_A 40 may transmit the mobility type of the UE_A 10 after thechange while being included in the tenth identification information.

Note that a method of changing the mobility type of the UE_A 10 is notlimited to the above.

Based on the reception of the bearer resource modification requestmessage and/or the determination of a mobility type, the MME_A 40transmits a bearer resource command message to the SGW_A 35 (S2404).

The MME_A 40 may transmit at least the ninth identification informationand/or the tenth identification information while being included in thebearer resource command message.

Here, in the description above, the MME_A 40 is described as determiningchange of the mobility type of the UE_A 10, but in place of the MME_A40, the PGW_A 30 may determine the change of the mobility type of theUE_A 10. In this case, the MME_A 40 may transmit the bearer resourcecommand message without including the tenth identification information.

The SGW_A 35 receives the bearer resource command message. Further,based on the reception of the bearer resource command message, the SGW_A35 acquires the ninth identification information and/or the tenthidentification information.

Based on the reception of the bearer resource command message, the SGW_A35 transmits the bearer resource command message to the PGW_A 30(S2406).

The SGW_A 35 may transmit at least the ninth identification informationand/or the tenth identification information while being included in thebearer resource command message.

The PGW_A 30 receives the bearer resource command message. Further,based on the reception of the bearer resource command message, the PGW_A30 acquires the ninth identification information and/or the tenthidentification information.

Based on information included in the bearer resource command messageand/or the subscriber information and/or the operator policy and/or theidentification information held by the PGW_A 30, the PGW_A 30 maydetermine change of a mobility type with respect to the UE_A 10 and/or amobility type of the UE_A 10 after the change.

For example, the PGW_A 30 may determine the mobility type indicated bythe ninth identification information as the mobility type of the UE_A 10after the change.

Instead of the mobility type indicated by the ninth identificationinformation, the PGW_A 30 may determine the default mobility type and/ora mobility type based on the subscriber information or the operatorpolicy as a mobility type of the UE_A 10 after the change.

Note that the PGW_A 30 may indicate any type from among the first toseventh types and/or a type obtained by combining any of the first toseventh types as the mobility type of the UE_A 10.

The PGW_A 30 may indicate a type other than the first to seventh typesinstead of any type from among the first to seventh types as themobility type of the UE_A 10.

Note that the mobility type of the UE_A 10 may be a mobility typecorresponding to the PDN connection, a mobility type corresponding tothe default bearer, or a mobility type corresponding to the EPS bearer.

The PGW_A 30 may transmit the mobility type of the UE_A 10 after thechange while being included in the tenth identification information.

Note that a method of changing the mobility type of the UE_A 10 is notlimited to the above.

Here, in the description above, a case is described that the PGW_A 30determines change of the mobility type of the UE_A 10, but in a casethat the MME_A 40 determines the change of the mobility type of the UE_A10, the PGW_A 30 may not determine the change of the mobility type ofthe UE_A 10.

In other words, in the case that the PGW_A 30 has received the tenthidentification information, the PGW_A 30 may not determine change of themobility type of the UE_A 10.

Based on the reception of the bearer resource command message and/or thedetermination of a mobility type, the PGW_A 30 transmits an updatebearer request message to the SGW_A 35 (S2410).

The PGW_A 30 may include at least the tenth identification informationin the update bearer request message.

Note that the update bearer request message may be a response messagecorresponding to the bearer resource command message.

The SGW_A 35 receives the update bearer request message. Further, basedon the reception of the update bearer request message, the SGW_A 35acquires the tenth identification information.

Based on the reception of the update bearer request message, the SGW_A35 transmits the update bearer request message to the MME_A 40 (S2412).

The SGW_A 35 may include at least the tenth identification informationin the update bearer request message.

The MME_A 40 receives the update bearer request message. Further, basedon the reception of the update bearer request message, the MME_A 40acquires the tenth identification information.

Based on the reception of the update bearer request message, the MME_A40 transmits a modify EPS bearer context request message to the eNB_A 45(S2414).

The MME_A 40 may include at least the tenth identification informationin the modify EPS bearer context request message.

Note that the modify EPS bearer context request message may be aresponse message to the bearer resource modification request message.

The eNB_A 45 receives the modify EPS bearer context request message andtransmits to the UE_A 10 an RRC message including the modify EPS bearercontext request message (S2416). Note that the RRC message may be an RRCconnection reconfiguration request message.

The UE_A 10 receives the RRC message including the modify EPS bearercontext request message. Further, in a case that the tenthidentification information is included in the modify EPS bearer contextrequest message, the UE_A 10 acquires respective pieces ofidentification information.

Based on the reception of the modify EPS bearer context request messageand/or the information included in the modify EPS bearer context requestmessage, the UE_A 10 may identify approval of change of the mobilitytype of the UE_A 10 and/or a mobility type of the UE_A 10 after thechange.

More specifically, based on the reception of the tenth identificationinformation, the UE_A 10 may identify that change of the mobility typeof the UE_A 10 has been approved.

The UE_A 10 may identify the mobility type indicated by the receivedtenth identification information as the mobility type of the UE_A 10after the change.

In order to respond to the received RRC message, the UE_A 10 transmitsan RRC message to the eNB_A 45 (S2418). The RRC message may be an RRCconnection reconfiguration complete message.

The eNB_A 45 receives an RRC connection reconfiguration message, andtransmits a bearer configuration message to the MME_A 40 based on thereception (S2420).

In addition, based on the reception of the modify EPS bearer contextrequest message, the UE_A 10 transmits the RRC message including amodify EPS bearer context accept message to the eNB_A 45 (S2422). Here,the modify EPS bearer context accept message may be a response messageto the modify EPS bearer context request message.

Note that the RRC message to be transmitted while including the modifyEPS bearer context accept message may be a Direct Transfer message.

The eNB_45 receives the RRC message including the modify EPS bearercontext accept message and transmits the modify EPS bearer contextaccept message to the MME_A 40 (S2424).

The MME_A 40 receives the modify EPS bearer context accept message.

Based on the reception of the modify EPS bearer context accept message,the MME_A 40 may transmit a modify bearer response message to the SGW_A35 (S2426).

Note that the modify bearer response message may be a response messageto the modify bearer request message.

The SGW_A 35 receives the modify bearer response message.

Based on the reception of the modify bearer response message, the SGW_A35 transmits the modify bearer response message to the PGW_A 30 (S2428).

The PGW_A 30 receives the modify bearer response message.

By the above-described steps, the UE_A 10 and/or the core network_A 90completes the first mobility type change procedure. According to thecompletion of the first mobility type change procedure, the UE_A 10and/or the core network_A 90 may change the mobility type of the UE_A10.

Note that by the first mobility type change procedure, the UE_A 10 canstore the received mobility type of the UE_A 10 after the change in anyUE context described with reference to any of FIGS. 21(b) to 21(d).

More specifically, by the first mobility type change procedure, the UE_A10 can acquire the mobility type of the UE_A 10 after the change fromthe core network_A 90, and store the mobility type in a UE context foreach PDN connection and/or a UE context for each bearer.

By the first mobility type procedure, the MME_A 40 can store themobility type of the UE_A 10 after the change in an MME context for eachPDN connection and/or an MME context for each bearer.

By the first mobility type procedure, the SGW_A 35 and/or the PGW_A 30can store the mobility type of the UE_A 10 after the change in an EPSbearer context for each PDN connection and/or an EPS bearer context foreach EPS bearer.

1.3.2.2 Second Mobility Type Change Procedure Example

The second mobility type change procedure is a mobility type changeprocedure initiated by the core network_A 90.

Examples of steps of the second mobility type change procedure will bedescribed below with reference to FIG. 25.

The MME_A 40 may transmit a bearer resource command message to the SGW_A35 (S2504).

The MME_A 40 may transmit at least the ninth identification informationwhile being included in the bearer resource command message.

By transmitting the bearer resource command message while including theninth identification information, the MME_A 40 may request change of themobility type of the UE_A 10 or indicate a mobility type of the UE_A 10after the requested change.

For example, the MME_A 40 may request change of the mobility type of theUE_A 10 to any type from among the first to seventh types and/or a typeobtained by combining any of the first to seventh types, or may requestchange of the mobility type to a type other than the first to seventhtypes instead of any type from among the first to seventh types.

The SGW_A 35 receives the bearer resource command message. Further,based on the reception of the bearer resource command message, the SGW_A35 acquires the ninth identification information.

Based on the reception of the bearer resource command message, the SGW_A35 may transmit the bearer resource command message to the PGW_A 30(S2506).

The SGW_A 35 may transmit at least the ninth identification informationwhile being included in the bearer resource command message.

The PGW_A 30 receives the bearer resource command message. Further,based on the reception of the bearer resource command message, the PGW_A30 acquires the ninth identification information.

Based on the reception of the bearer resource command message, the PGW_A30 transmits an update bearer request message to the SGW_A 35 (S2510).

The PGW_A 30 may include at least the ninth identification informationin the update bearer request message.

Note that the PGW_A 30 may transmit the update bearer request message tothe SGW_A 35 based on the operator policy and the subscriberinformation, not based on the reception of the bearer resource commandmessage.

In other words, the PGW_A 30 may start the second mobility type changeprocedure, based on the operator policy or the subscriber information,not based on the reception of the bearer resource command message.

In this case, the bearer resource command message that the MME_A 40and/or the SGW_A 35 and/or the PGW_A 30 transmit and/or receive can beomitted.

By transmitting the update bearer request message including the ninthidentification information, the PGW_A 30 may request change of themobility type of the UE_A 10 or indicate a mobility type of the UE_A 10after the requested change.

For example, the PGW_A 30 may request change of the mobility type of theUE_A 10 to any type from among the first to seventh types and/or a typeobtained by combining any of the first to seventh types, or may requestchange of the mobility type to a type other than the first to seventhtypes instead of any type from among the first to seventh types.

The SGW_A 35 receives the update bearer request message. Further, basedon the reception of the update bearer request message, the SGW_A 35acquires the ninth identification information.

Based on the reception of the update bearer request message, the SGW_A35 transmits the update bearer request message to the MME_A 40 (S2512).

The SGW_A 35 may include at least the ninth identification informationin the update bearer request message.

The MME_A 40 receives the update bearer request message. Further, basedon the reception of the update bearer request message, the MME_A 40acquires the ninth identification information.

Based on the reception of the update bearer request message, the MME_A40 transmits a modify EPS bearer context request message to the eNB_A 45(S2514).

The MME_A 40 may include at least the ninth identification informationin the modify EPS bearer context request message.

By transmitting the modify EPS bearer context request message includingthe ninth identification information, the MME_A 40 may request change ofthe mobility type of the UE_A 10 or indicate a mobility type of the UE_A10 after the requested change.

The ninth identification information may be information indicating amobility type which is different from the mobility type indicated by thesecond identification information and/or the fourth identificationinformation and/or the sixth identification information that the MME_A40 and/or the PGW_A 30 has previously transmitted to the UE_A 10.

Further, the ninth identification information may be informationindicating a different mobility type from the mobility type indicated bythe second identification information and/or the fourth identificationinformation and/or the sixth identification information that the MME_A40 and/or the PGW_A 30 has stored.

The eNB_A 45 receives the modify EPS bearer context request message andtransmits to the UE_A 10 an RRC message in which the modify EPS bearercontext request message is included (S2516). Note that the RRC messagemay be an RRC connection reconfiguration request message.

The UE_A 10 receives the RRC message including the modify EPS bearercontext request message. Further, in a case that the ninthidentification information is included in the modify EPS bearer contextrequest message, the UE_A 10 acquires respective pieces ofidentification information.

Based on the reception of the modify EPS bearer context request messageand/or the information included in the modify EPS bearer context requestmessage and/or the identification information held by the UE_A 10, theUE_A 10 may determine change of the mobility type of the UE_A 10 and/ora mobility type of the UE_A 10 after the change.

For example, the UE_A 10 may determine the mobility type indicated bythe ninth identification information as a mobility type of the UE_A 10after the change.

Alternatively, in place of the mobility type indicated by the ninthidentification information, the UE_A 10 may determine a mobility typedesired by the UE_A 10 as a mobility type of the UE_A 10 after thechange.

Note that the UE_A 10 may indicate any type from among the first toseventh types and/or a type obtained by combining any of the first toseventh types as a mobility type of the UE_A 10.

Further, the UE_A 10 may indicate a type other than the first to seventhtypes instead of any type from among the first to seventh types.

Note that the mobility type of the UE_A 10 may be a mobility typecorresponding to the PDN connection or a mobility type corresponding tothe default bearer.

The UE_A 10 may transmit the mobility type of the UE_A 10 after thechange while being included in the tenth identification information.

Note that a method of changing the mobility type of the UE_A 10 is notlimited to the above.

In order to respond to the received RRC message, the UE_A 10 transmitsthe RRC message to the eNB_A 45 (S2518). The RRC message may be an RRCconnection reconfiguration complete message.

The eNB_A 45 receives an RRC connection reconfiguration message, andtransmits a bearer configuration message to the MME_A 40 based on thereception (S2520).

Based on the reception of the modify EPS bearer context request message,the UE_A 10 transmits the RRC message including a modify EPS bearercontext accept message to the eNB_A 45 (S2522).

The UE_A 10 may transmit at least the tenth identification informationwhile being included in the modify EPS bearer context accept message.

Here, the modify EPS bearer context accept message may be a responsemessage to the modify EPS bearer context request message.

Note that the RRC message to be transmitted while including the modifyEPS bearer context accept message may be a Direct Transfer message.

The eNB_45 receives the RRC message including the modify EPS bearercontext accept message and transmits the modify EPS bearer contextaccept message to the MME_A 40 (S2524).

The MME_A 40 receives the modify EPS bearer context accept message.Further, based on the reception of the modify EPS bearer context acceptmessage, the MME_A 40 acquires the tenth identification information.

Based on the reception of the modify EPS bearer context accept messageand/or the information included in the modify EPS bearer context acceptmessage, the MME_A 40 may identify approval of change of the mobilitytype of the UE_A 10 and/or a mobility type of the UE_A 10 after thechange.

More specifically, based on the reception of the tenth identificationinformation, the MME_A 40 may identify that change of the mobility typeof the UE_A 10 has been approved.

The MME_A 40 may identify the mobility type indicated by the receivedtenth identification information as a mobility type of the UE_A 10 afterthe change.

Based on the reception of the modify EPS bearer context accept message,the MME_A 40 transmits a modify bearer response message to the SGW_A 35(S2526).

The MME_A 40 may transmit at least the tenth identification informationwhile being included in the modify bearer response message.

Note that the modify bearer response message may be a response messageto the modify bearer request message.

The SGW_A 35 receives the modify bearer response message. Further, basedon the reception of the modify bearer response message, the SGW_A 35acquires the tenth identification information.

Based on the reception of the modify bearer response message, the SGW_A35 transmits the modify bearer response message to the PGW_A 30 (S2528).

The SGW_A 35 may transmit at least the tenth identification informationwhile being included in the modify bearer response message.

The PGW_A 30 receives the modify bearer response message. Further, basedon the reception of the modify bearer response message, the PGW_A 30acquires the tenth identification information.

Based on the reception of the modify EPS bearer context accept messageand/or the information included in the modify EPS bearer context acceptmessage, the PGW_A 30 may identify approval of change of the mobilitytype of the UE_A 10 and/or a mobility type of the UE_A 10 after thechange.

More specifically, based on the reception of the tenth identificationinformation, the PGW_A 30 may identify that change of the mobility typeof the UE_A 10 has been approved.

The PGW_A 30 may identify the mobility type indicated by the receivedtenth identification information as a mobility type of the UE_A 10 afterthe change.

By the above-described steps, the UE_A 10 and/or the core network_A 90completes the second mobility type change procedure. According to thecompletion of the second mobility type change procedure, the UE_A 10and/or the core network_A 90 may change the mobility type of the UE_A10.

Note that by the second mobility type change procedure, the UE_A 10 canstore the mobility type of the UE_A 10 after the change in any UEcontext described with reference to any of FIGS. 21(b) to 21(d).

More specifically, by the second mobility type change procedure, theUE_A 10 can store the mobility type of the UE_A 10 after the change in aUE context for each PDN connection and/or a UE context for each bearer.

Further, by the second mobility type change procedure, the MME_A 40 canacquire the mobility type of the UE_A 10 after the change from the UE_A10 and store the mobility type in an MME context for each PDN connectionand/or an MME context for each bearer.

By the second mobility type change procedure, the SGW_A 35 and/or thePGW_A 30 can acquire the mobility type of the UE_A 10 after the changefrom the UE_A 10 and store the mobility type in an EPS bearer contextfor each PDN connection and/or an EPS bearer context for each EPSbearer.

1.3.2.3. Modified Examples of Mobility Type Change Procedure

Regarding the core network_A 90 in the mobility type change procedureexample described above, a transmission and/or reception method changeprocedure is described for a case adopting a core network configured toinclude the MME_A 40, the SGW_A 35, and the PGW_A 30 described withreference to FIG. 2; however, the core network_A 90 may be configured toinclude different devices from the MME_A 40, the SGW_A 35, and the PGW_A30.

In this case, an NAS message, such as the bearer resource modificationrequest message or the modify EPS bearer context accept messagedescribed in the present procedure and transmitted by the UE_A 10, isreceived not by the MME_A 40 but another device in the core network_A90.

Accordingly, the reception and the processes of the NAS message by theMME_A 40 in the above description can be replaced with those performedby a device in the core network_A 90.

Furthermore, the transmission and the processes of the NAS message suchas the modify EPS bearer context request message by the MME_A 40 in theabove description can be replaced with those performed by the device inthe core network_A 90.

1.3.3. Examples of Handover Procedure

The UE_A 10 and/or the core network_A 90 may perform a handoverprocedure, based on a mobility type of the UE_A 10.

For example, in a case that a connection is established by a mobilitytype supporting handover in an active mode, the UE_A 10 may perform ahandover procedure and continue communication by switching theconnection to a different base station.

Alternatively, in a case that a connection is established by a mobilitytype that does not allow handover in an active mode, the UE_A 10 may, inthe handover procedure, receive a control message for disconnectingcommunication from the core network_A 90, for example, and performdisconnection from the PDN connection or detach from the core network_A90. Note that in this case, the UE_A 10 may delete the UE context.Meanwhile, the MME_A 40 may delete the MME context for the UE_A 10.

For example, in the case that a connection is established by a mobilitytype supporting handover in an active mode, the UE_A 10 may perform thehandover procedure and continue communication by switching theconnection to a different base station.

Alternatively, in the case that a connection is established by amobility type that does not allow handover in an active mode, the UE_A10 may, in the handover procedure, receive a control message fordisconnecting communication from the core network_A 90, for example, andperform disconnection from the PDN connection or detach from the corenetwork_A 90. Note that in this case, the UE_A 10 may delete the UEcontext. Meanwhile, the MME_A 40 may delete the MME context for the UE_A10.

In a case that a different mobility type has been determined for eachPDN connection, the UE_A 10 may perform a different process for each PDNconnection at the time of handover.

For example, for a PDN connection established by a mobility type thatsupports handover in an active mode, the UE_A 10 may perform a handoverprocedure and continue communication by switching the connection to adifferent base station.

Alternatively, for a PDN connection established by a mobility type thatdoes not allow handover in an active mode, the UE_A 10 may, in thehandover procedure, receive a control message for disconnectingcommunication from the core network_A 90, for example, and disconnectthe PDN connection.

At this time, the core network_A 90 may transmit, while being includedin the control message, information for identifying the PDN connectionto be disconnected. Note that a control device in the core network_A 90transmitting the control message may be the MME_A 40. The UE_A 10 mayidentify the PDN connection to be disconnected based on the receivedinformation.

Here, the information for identifying a PDN connection may be a bearerID and/or an APN and/or an IP address, or the like.

Alternatively, information for identifying a PDN connection may be amobility type. The UE_A 10 may receive a mobility type and select a PDNconnection conforming to the received mobility type, based on the UEcontext.

Further, when disconnecting the PDN connection, the UE_A 10 may delete,from the UE context, information corresponding to the PDN connection tobe disconnected. Meanwhile, the MME_A 40 may delete, in the MME contextfor the UE_A 10, information corresponding to the PDN connection to bedisconnected.

For example, in the case that a connection is established by a mobilitytype supporting handover in an active mode, the UE_A 10 may perform thehandover procedure and continue communication by switching theconnection to a different base station.

Alternatively, in the case that a connection is established by amobility type that does not allow handover in an active mode, the UE_A10 may, in the handover procedure, receive a control message fordisconnecting communication from the core network_A 90, for example, andperform disconnection from the PDN connection or detach from the corenetwork_A 90. Note that in this case, the UE_A 10 may delete the UEcontext. Meanwhile, the MME_A 40 may delete the MME context for the UE_A10.

Note that the control message for deleting a PDN connection and/or acontrol message for detach of the UE_A 10 described above may not be acontrol message that the core network_A 90 transmits to the UE_A 10 atthe handover.

For example, such a control message may be a response message to atracking area update request transmitted by the UE_A 10, a detachrequest message, or a delete bearer request message.

Further, in a case that a base station to which the UE_A 10 is connectedhas changed due to movement of the UE_A 10, the UE_A 10 may delete amobility type that does not allow handover in an active mode and/or aPDN connection of a mobility type that does not allow handover in anidle mode. Further, in the deletion of the PDN connection, informationcorresponding to the PDN connection to be deleted, which is included inthe UE context, may be deleted. Such information corresponding to thePDN connection may be a bearer ID, an IP address, an APN, and the like.

As described above, communication control corresponding to a mobilitytype may be performed.

2. Modified Example

A program running on each apparatus or device according to the presentinvention may be a program for controlling a Central Processing Unit(CPU) and the like to cause a computer to function so as to enable thefunctions of the embodiments of the present invention. Such a program orinformation used in the program is stored temporarily in a volatilememory such as a Random Access Memory (RAM), a non-volatile memory suchas a flash memory, a Hard Disk Drive (HDD), or other storage devicesystems.

Note that a program for enabling the functions of the embodiments of thepresent invention may be recorded in a computer-readable recordingmedium. This program recorded in the recording medium may be read by acomputer system to be performed, thereby enabling the functions. It isassumed that the “computer system” refers to a computer system builtinto a device, and the computer system includes an OS and hardwarecomponents such as a peripheral device. Further, the “computer-readablerecording medium” may be a semiconductor recording medium, an opticalrecording medium, a magnetic recording medium, a medium that holds aprogram dynamically for a short period of time, or othercomputer-readable recording media.

Further, respective functional blocks or various characteristics of theapparatuses and devices used in the embodiments above may be implementedor performed by an electric circuit, for example by an integratedcircuit or by multiple integrated circuits. An electric circuit designedto perform the functions described in this specification may include ageneral-purpose processor, a digital signal processor (DSP), anapplication specific integrated circuit (ASIC), a field programmablegate array (FPGA), or other programmable logic devices, discrete gatesor transistor logic, discrete hardware components, or a combination ofthese. The general-purpose processor may be a microprocessor, or aprocessor of a known type, a controller, a micro-controller, or a statemachine. The electric circuits described above may include digitalcircuits or analog circuits. Furthermore, in a case where with advancesin semiconductor technology, a circuit integration technology with whichthe current integrated circuits are replaced appears, the presentinvention can also adopt a new integrated circuit based on thetechnology.

Note that the invention of the present patent application is not limitedto the above-described embodiments. In the embodiments, the apparatuseshave been described as examples, but the present invention is notlimited to such apparatuses, and is applicable to a fixed-type or astationary-type electronic apparatus installed indoors or outdoors, forexample, a terminal apparatus or communication device such as anAudio-Video (AV) apparatus, a kitchen apparatus, a cleaning or washingmachine, an air-conditioning apparatus, office equipment, a vendingmachine, and other household apparatuses.

The embodiments of the present invention have been described in detailabove referring to the drawings, but the specific configuration is notlimited to the embodiments and includes, for example, an amendment to adesign that falls within the scope that does not depart from the gist ofthe present invention. Furthermore, various modifications are possiblewithin the scope of the present invention defined by claims, andembodiments that are made by suitably combining technical meansdisclosed according to the different embodiments are also included inthe technical scope of the present invention. Furthermore, aconfiguration in which a constituent element that achieves the sameeffect is substituted for the one that is described according to theembodiments is also included in the technical scope of the presentinvention.

REFERENCE SIGNS LIST

-   1 Communication system-   5 PDN_A-   10 UE_A-   20 UTRAN_A-   22 eNB (UTRAN)_A-   24 RNC_A-   25 GERAN_A-   26 BSS_A-   30 PGW_A-   35 SGW_A-   40 MME_A-   45 eNB_A-   50 HSS_A-   55 AAA_A-   60 PCRF_A-   65 ePDG_A-   70 WLAN ANa-   72 WLAN APa-   74 TWAG_A-   75 WLAN ANb-   76 WLAN APb-   80 LTE AN_A-   90 Core network_A-   100 CIOT AN_A

The invention claimed is:
 1. A User Equipment (UE) comprising: a memory;a controller; and transmission and/or reception circuitry, wherein thetransmission and/or reception circuitry is configured to receive anaccept message from a core network via a base station within a radioaccess network, the accept message includes a first information, thememory is configured to store the first information, the transmissionand/or reception circuitry is configured to receive, from the corenetwork via the base station within the radio access network, a controlmessage including a second information in an update procedure initiatedby the core network, the first information and the second informationare information that restrict mobility handling of the UE, and thecontroller is configured to replace the first information in the memorywith the second information during the update procedure.
 2. Acommunication method performed by a User Equipment (UE), thecommunication method comprising: receiving an accept message from a corenetwork via a base station within a radio access network, wherein theaccept message includes a first information; storing the firstinformation; receiving, from the core network via the base stationwithin the radio access network, a control message including a secondinformation in an update procedure initiated by the core network; andreplacing the first information in the UE with the second informationduring the update procedure, wherein the first information and thesecond information are information that restrict mobility handling ofthe UE.
 3. A core network apparatus comprising: a memory; a controller;and transmission and/or reception circuitry, wherein the transmissionand/or reception circuitry is configured to transmit an accept message,via a base station within a radio access network, to a User Equipment(UE), the accept message includes a first information, the transmissionand/or reception circuitry is configured to transmit to the UE, via thebase station within the radio access network, a control messageincluding a second information in an update procedure initiated by thecore network, the first information and the second information areinformation that restrict mobility handling of the UE, and thecontroller is configured to replace the first information in the memorywith the second information during the update procedure.
 4. Acommunication method performed by a core network, the communicationmethod comprising: transmitting an accept message to a User Equipment(UE) via a base station within a radio access network, wherein theaccept message includes a first information; replacing the firstinformation in the core network with a second information during anupdate procedure initiated by the core network; and transmitting acontrol message including the second information via the base stationwithin the radio access network to the UE in the update procedure,wherein the first information and the second information are informationthat restrict mobility handling of the UE.